Stream Deck and remote control

The Signal API

Voco's Signal API lets external devices send commands to the active stream without opening the admin dashboard. It is available on Voco Pro and Network plans.

The API supports five actions: stream:start, stream:stop, captions:clear, captions:hide, and captions:show.

Stream Deck setup (URL action)

For tools that support custom HTTP headers, use POST with an Authorization header. This keeps your API key out of URLs, browser history, and server logs.

Stream Deck's basic Website button can still use a URL trigger when no header-based action is available, but treat that button profile like a password and rotate the key if it is shared.

1. 1Find your API keyOpen Settings → API in the Voco dashboard and copy your church API key.
2. 2Use a header-capable action where possibleSet the method to POST, the URL to https://voco.church/api/v1/signal, and add Authorization: Bearer YOUR_KEY.
3. 3Send the actionSend JSON such as { "action": "stream:start" } for each button.
4. 4Fallback only: URL triggerIf your tool cannot send headers, use the URL format below and keep the Stream Deck profile private.
5. 5Repeat for each actionCreate one button per action — start, stop, captions on/off, clear.

Bitfocus Companion

Bitfocus Companion supports HTTP request actions, which work with the Signal API's POST endpoint. Use a Generic HTTP Request button and set the method to POST, the URL to https://voco.church/api/v1/signal, and send either an Authorization header or a JSON body with your API key and action.

Companion is useful when you need a full button grid controller rather than a consumer Stream Deck, or when integrating with ATEM, vMix, or ProPresenter control workflows.

ProPresenter URL actions

ProPresenter slides can fire URL actions when shown. Add a URL action to any slide using the Signal API GET endpoint — for example, a pre-service slide that starts the Voco stream automatically when it is put to screen.