Organization rate limits

The /v1/organizations/rate_limits endpoint returns the rate limits applied at the organization level for the Messages API and its supporting resources. Limits for other products, such as Claude Managed Agents, are not included.

Key concepts

• Rate limit groups: Each entry in the response represents one rate limit group. Model rate limits are grouped so that several model versions share a single set of limits, and other groups cover resources such as the Message Batches API, the Files API, the Token Counting API, agent skills, and the web search tool.
• group_type: Identifies which category of limits the entry covers. See Filtering by group type for the list of values.
• models list: For model_group entries, the models field lists every model ID and alias that counts against that group's limits. Use this list to look up which group any model string falls under. For other group types, models is null.
• limits list: Each group carries a list of {type, value} pairs. The type field identifies the limiter (such as requests_per_minute, input_tokens_per_minute, or output_tokens_per_minute) and value is the configured limit. See Rate limits for how each limiter is measured and enforced.

For complete parameter details and response schemas, see the Organization Rate Limits API reference.

List all organization rate limits

Look up the limits for a specific model

Pass any model ID or alias as the model query parameter to return only the entry that contains it:

If the model string doesn't match any group, the endpoint returns a 404 error. The model parameter is supported on the organization endpoint only; the workspace endpoint doesn't accept it.

Workspace rate limits

The /v1/organizations/workspaces/{workspace_id}/rate_limits endpoint returns the rate limit overrides configured for a single workspace.

The response only includes overrides, so anything missing from it is inherited from the organization:

• A group that is absent from data has no workspace override at all. The workspace inherits the organization-level limits for that group (it is not unlimited).
• Within a group that is present, a limiter type that is absent from limits[] has no workspace override for that limiter. The workspace inherits the organization value for it.
• For each limiter that is present, org_limit is the organization-level value for the same limiter, or null if the organization has no configured limit for that limiter type.

For complete parameter details and response schemas, see the Workspace Rate Limits API reference.

Filtering by group type

Both endpoints accept an optional group_type query parameter that restricts the response to a single category:

Valid values are model_group, batch, token_count, files, skills, and web_search.

Pagination

Both endpoints accept a page query parameter and return a next_page field. Responses are currently always a single page, so next_page is null. Loop on next_page so your client paginates correctly without changes when the response grows.

Frequently asked questions

Which model strings appear in the models list?

Every model ID and alias that counts against the group, including dated IDs (such as claude-sonnet-4-5-20250929) and undated aliases (such as claude-sonnet-4-5). Look up any model string you pass to the Messages API and you'll find it in exactly one model_group entry.

What does it mean if a group is missing from the workspace response?

The workspace has no override for that group and inherits the organization-level limit. Query the organization endpoint to see the inherited values.

Can I update rate limits with this API?

No. To set workspace rate limits, open the workspace in the Claude Console and use the Limits tab.

See also

• Rate limits
• Admin API
• Admin API reference
• Workspaces
• Usage and Cost API