API reference

The Videohati REST API lives under https://api.videohati.com/v1. This reference covers what an API-key developer calls: videos, the multipart upload flow, playback session creation, and webhook endpoint management. The staging host is https://api.staging.videohati.com.

Authentication

Every call you make uses one credential:

• API key — Authorization: Bearer vh_live_... (live mode) or Authorization: Bearer vh_test_... (test mode). Keys are scoped to a single project and carry read and/or write scopes. You create and manage keys in the dashboard.

The player authenticates its own calls with the short-lived session token your server creates — you never call those endpoints yourself.

The in-page playground sends live requests with a vh_test_ key. It rejects vh_live_ keys so you never run a production-mode request from the docs.

Start from the Quickstart to get a test key end to end, or pick a client under SDKs to see how each language handles this for you.

Errors

Every error uses one envelope:

{ "error": { "code": "<machine_code>", "message": "<human text>" } }

See Errors for the status-code map and the shared codes.

Pagination

List endpoints accept limit (1–100, default 25) and an opaque cursor. The response carries nextCursor when more pages exist.

Rate limits

Rate-limited operations return 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and Retry-After headers. The per-operation pages list the limit that applies.

Webhooks

Registered endpoints receive HMAC-signed event deliveries. See Events for the envelope, the event names, and how to verify a signature.