# External data

<figure><img src="https://2100860514-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5xSBdLnIwNcJR5fryFDs%2Fuploads%2FeJ0DtDqFxjgKmsL3c2UU%2Fexternal%20in%20editor.jpg?alt=media&#x26;token=f20096c2-1dbc-4c5f-b9a8-60e48661af1c" alt=""><figcaption><p>In the editor, we getfeedback on the external data</p></figcaption></figure>

<figure><img src="https://2100860514-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5xSBdLnIwNcJR5fryFDs%2Fuploads%2FEfIAxPtaKblffjCfGqeK%2Fexternal%20in%20timer.jpg?alt=media&#x26;token=b9557d51-020c-49ce-b607-8d7df2bd9d84" alt=""><figcaption><p>The external data is shown in the timer, and can be hidden in the view settings</p></figcaption></figure>

You can inject data into the ontime presenter view. This is useful in cases where you would like another software to push some data to Ontime. ie: a running time from video playback in VLC

## Setting external data

You can set the external fields using both the OSC or WebSocket API, again the APIs are fully compatible

## OSC

| Message                              | Payload       |
| ------------------------------------ | ------------- |
| /ontime/set-external-message-text    | string        |
| /ontime/set-external-message-visible | true \| false |

WebSocket

| Message                      | Payload       |
| ---------------------------- | ------------- |
| set-external-message-text    | string        |
| set-external-message-visible | true \| false |