External clients authenticate with Marker-issued API tokens.
Developer platform
Build your own Marker capture workflow.
The Marker API gives external clients a token-authenticated REST surface for sessions, sub-sessions, tags, markers, chapter markers, timeline reads, and integration context.
Best for
Custom tools
Auth model
Bearer API token
Core route
/v1/integrations/stream-deck/context
API
Developer platform
1
Create an API token from Marker.
2
Choose the environment for your client.
3
Read sessions, sub-sessions, tags, and active context.
4
Create markers or chapter markers from your custom tool.
Best for
Custom tools
Auth model
Bearer API token
Core route
/v1/integrations/stream-deck/context
Scopes include sessions, sub-sessions, tags, markers, and chapter markers.
The integration context endpoint returns sessions, sub-sessions, tags, active sub-sessions, and Twitch channel state for external controls.
Workflow
How API works with Marker
- 1
Create an API token from Marker.
- 2
Choose the environment for your client.
- 3
Read sessions, sub-sessions, tags, and active context.
- 4
Create markers or chapter markers from your custom tool.
Setup
Get started
Create a Marker API token in the app.
Store the token securely in your integration.
Send it as a Bearer token to the Marker REST API.
Request only the scopes your workflow needs.
Use cases
Where it fits
Connect a custom hardware controller.
Send marker records from a production script.
Build dashboards or pickers from Marker session context.
FAQ
API questions
How do external clients authenticate?
External clients use Marker-issued API tokens in the Authorization header. Marker stores token secrets as hashes and only shows the plaintext token once.
What can the API read and write?
The API exposes scoped access for sessions, sub-sessions, tags, markers, chapter markers, timelines, and integration context.
Can API tokens manage other API tokens?
No. Token management is handled in Marker and is intentionally not exposed through PAT-authenticated REST endpoints.