Services, entitlements and usage

Use /v1/workspaces/{workspace_id}/api-entitlements to inspect API availability and limits, and /api-usage or /api-usage/requests for authorized usage reporting. Plan names and limits can change; inspect current entitlement data instead of hard-coding marketing labels.

Workspace services

List/read services with services:read and inspect service usage with services:usage:read. Service creation and editing, time entries, corrections, voiding, and resource-service assignment use separate write operations and permissions. See the reference for each body and response.

A time-entry void operation is distinct from editing an entry. Preserve returned IDs and consult current state before retrying a mutation after a timeout. Do not assume all service operations support the project API's idempotency contract.

Rate limits and retention

A 429 response can indicate a quota or request-rate boundary. Honor Retry-After when provided and use bounded backoff. Increasing request volume or rotating keys does not bypass workspace policy. For logs, age and storage retention can remove events even after ingestion succeeded.

If a capability is unavailable, check workspace service grants, current membership, credential scopes, and plan entitlements in the portal. Upgrading a plan does not automatically broaden an existing key's scopes.