Skip to main content
Cor has two REST APIs:

Session Reporting

List sessions and download transcripts for reporting.

User Context

Push extra context about an onboardee so Obi can personalise sessions.
Both are server-side APIs. Do not call them from the browser. That would expose your token.

​
Base URL

https://app.coragents.ai

​
Authentication

Every request must include an Authorization header using the Token scheme: 
Authorization: Token <your-api-token>
Tokens are provisioned by the Cor team. The reporting token and the onboardee-context token may be different. See Authentication. 
curl -s -H "Authorization: Token <your-api-token>" \
  "https://app.coragents.ai/api/sessions/reporting?limit=5"
In the playground on each endpoint page, paste your full header value (including the word Token) into the Authorization field.

​
Errors

Errors return a JSON body with an error object: 
{
  "error": {
    "code": "not_found",
    "message": "Transcript not available."
  }
}
StatusMeaning
400Invalid request (bad body or parameter).
401Missing or invalid token.
404Resource not found or not available.
429Rate limit exceeded.

​
Rate limiting

The reporting endpoints share an IP-based limit of 30 requests per 60 seconds. Over the limit, you get 429 with a retry_after_seconds value: 
{
  "error": {
    "code": "rate_limited",
    "message": "Too many requests. Please wait before trying again.",
    "details": {
      "retry_after_seconds": 42
    }
  }
}
Wait retry_after_seconds before retrying.

​
Pagination

GET /api/sessions/reporting is paginated. Use page and limit (max 100), and read total_pages from the response to know when to stop. Loop until page reaches total_pages.