Who should use the OpenAPI, recommended reading order, and prerequisites.
Use the Qoder OpenAPI to manage members, groups, and billing groups, and to query usage and AI code metrics at the organization level. All endpoints require an API Key and only expose data within the organization bound to that key.
Follow the sidebar under Account → OpenAPI:
Obtain
If an error occurs, capture
Who this is for
- Organization admins or integration / ops / data owners who need to pull organizational data into external systems.
- Callers comfortable with HTTPS, JSON, and REST.
Recommended reading order
Follow the sidebar under Account → OpenAPI:
- Conventions — Base URL, auth, pagination, errors, naming.
- Get API Key — Create a key in the console.
- API Key Security — Storage, rotation, and incident handling.
- Member APIs — Members, stats, quotas, and add-on caps.
- Group APIs — Groups and group membership.
- Billing Group APIs — Credits attribution, group limits, members, and period usage.
- Usage APIs — Credits usage events and rollups (member and org scope).
- AI Code Metrics & Tracking — Aggregates, commit attribution, detail and export APIs.
Scope (summary)
| Topic | Details |
|---|---|
| Auth | Authorization: Bearer <api_key>; the key is tied to an organization. |
| Data scope | Only data for that organization; fields per endpoint. |
| Base path | Most routes live under /v1/organizations/{organization_id} (see Conventions). |
Organization ID
Obtain organization_id from the organization settings or URL in the Qoder web console. Replace placeholder org_xxx in examples with your real ID.
Getting help
If an error occurs, capture requestId from the response body and share it with Qoder support.