Skip to main content
The Dubformer API uses API keys to authenticate requests. You can view and manage your API keys in the Dubformer Studio. All API requests must include your API key in the Authorization header:
Keep your API keys secure and do not share them in publicly accessible areas such as GitHub, client-side code, or public forums.

Example Request

Here’s an example request to list your projects:

Rate Limiting

The Dubformer API implements rate limiting to ensure fair usage and system stability. Current limits are:
  • 60 requests per minute per API key
  • 1000 requests per day per API key
If you exceed these limits, you’ll receive a 429 Too Many Requests response. The response will include Retry-After header indicating how many seconds to wait before making another request.

Project and video creation

Creating projects and videos is also rate limited per organization. Only projects and videos created through the API count, including those deleted later. Projects and videos created in Dubformer Studio don’t count. The windows are sliding. Contact your account manager if your organization needs higher limits. When a limit is reached, the request is rejected with 429 Too Many Requests. The Retry-After header holds the number of seconds until the next project or video can be created, and the body names the limit:

Error Responses

When authentication fails, you’ll receive one of the following error responses:
  • 400 Bad Request: Missing or invalid authorization token
  • 400 Bad Request: Access denied to this project
Example error response: