Use the Qoder Teams OpenAPI to query members, 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.
Who this is for
- Organization admins or integration / ops / data owners who need to pull Teams data into external systems.
- Callers comfortable with HTTPS, JSON, and REST.
Recommended reading order
Follow the sidebar under Account → OpenAPI (English docs place OpenAPI next to Teams):
- 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, add-on caps, usage limits.
- 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). |
An API Key has broadly the same access as its creator within the product’s permission model. Do not paste keys into repos, chat, or email.
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. 
