# Player — Native Picture-in-Picture (PiP) Request

The LiSA Player accepts message to either enter or exit native Picture-in-Picture.

This message is sent by the host app / environment to the LiSA Player.

### Properties

Along with all standard [Message properties](https://docs.hello-lisa.com/developers/guides/player-communication/message-api-reference/..#properties), a **Native PiP Request** message includes the following additional properties:

<table><thead><tr><th width="244" valign="top">Name</th><th width="192" valign="top">Type</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top"><code>messageType</code></td><td valign="top"><pre><code>Literal
</code></pre><p>Required.</p></td><td valign="top"><code>lsc:player:native-pip</code></td></tr><tr><td valign="top"><code>pipState</code></td><td valign="top"><pre><code>Enum
</code></pre><p>Required.</p></td><td valign="top"><p>The <code>pipState</code> property indicates the desired native Picture-in-Picture state.</p><p></p><ul><li><code>exitPip</code> — Leave currently active, native PiP window</li><li><code>requestPip</code> — Enter native PiP window</li></ul></td></tr></tbody></table>

***

### Type Definition

```typescript
interface PlayerNativePipRequestMessage extends Omit<
  Message,
  'messageType' | 'recipient'
> {
  messageType: 'lsc:player:native-pip';
  pipState: 'exitPip' | 'requestPip';
  recipient: 'LiSA';
}
```

***

### Examples

```json
{
  "messageType": "lsc:player:native-pip",
  "pipState": "requestPip",
  "recipient": "LiSA",
  "sender": "Example"
}
```