The Gumlet API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
The API uses Gumlet API tokens to authenticate requests. You can generate and manage your tokens in the dashboard on the API Keys page.
Authentication to the API is performed via HTTP Bearer Token Authentication. You can provide your token in
Authorization header in the following format
Authorization: Bearer <<apiKey>>
Gumlet servers enforce rate limits to ensure our APIs are responsive as we grow. The rate limit is tied to an account and set to 1000 requests per hour. If your team would like a higher rate limit, please reach out to our sales team.
Live video streaming features and APIs are in private alpha. Please contact us at [email protected] to try it out.
Gumlet API Error Codes are described in this document.