All Vidmob API requests must include a valid API key passed as a Bearer token in the Authorization header:
Authorization: Bearer <your-api-key>
Getting an API key
API keys are issued through the Vidmob ACS portal. If you don't yet have access, contact your Vidmob account team.
Once you have a key, store it securely — treat it like a password. Do not commit it to source control or expose it in client-side code.
Token scopes
Keys are scoped to control what operations they can perform:
| Scope | Access |
|---|---|
scoring:read | Read-only. Fetch scores, status, scorecards, and criteria. |
scoring:read_write | Full access. Includes submitting new media for scoring. |
Most integrations that submit assets need scoring:read_write. If your key returns 401 Unauthorized on write operations, confirm the scope with your Vidmob contact.
Error responses
A missing, expired, or scoped-out key returns a 401:
{
"statusCode": 401,
"message": "Request is Unauthorized",
"error": "Unauthorized"
}Common causes:
- Missing
Authorizationheader - Expired or revoked key
- Key lacks the required scope for the requested operation
Using your key in the API explorer
Click the lock icon on any endpoint page and enter your API key. It will be sent automatically with all requests made through the Try It console.