These docs are currently outdated. We’re actively working on updating them to reflect the latest version of Repixa. Some information may not be accurate.
Repixa API
The Repixa API lets you programmatically interact with your agents, trigger demo sessions, retrieve session data, and integrate Repixa into your own workflows.
Base URL
Authentication
All API requests require a Bearer token. You can generate an API key from your Repixa dashboard under Settings → API Keys.
Pass your key in the Authorization header on every request:
Authorization: Bearer YOUR_API_KEY
Example request:
curl https://api.repixa.io/v1/agents \
-H "Authorization: Bearer YOUR_API_KEY"
Keep your API key secret. Never expose it in client-side code or public repositories.
All responses are returned as JSON. Successful responses return a 2xx status code. Errors follow a consistent structure:
{
"error": {
"code": "unauthorized",
"message": "Invalid or missing API key."
}
}
Rate limits
| Plan | Requests per minute |
|---|
| Starter | 60 |
| Pro | 300 |
| Enterprise | Custom |
Exceeded rate limits return a 429 Too Many Requests response.
Versioning
The current API version is v1. Breaking changes will be released under a new version prefix (e.g. /v2). The previous version will be supported for at least 6 months after a new version ships.