Skip to main content
Every operation can return authentication, authorization, rate-limit and internal errors. Every write accepts an optional Idempotency-Key; conflicting reuse or an identical request still in progress returns 409. The table below adds resource-specific failures. The API Reference remains the source for exact fields and HTTP response schemas.

Context and projects

Groups and encrypted access

All operations below require a human principal. Group collaboration is also plan-gated. Authorization and encrypted-material completion are separate: a successful membership or grant write can report pending material without being an HTTP failure. See the access model. Use the SDK reconciliation flow for encrypted batches. Do not construct wrappers from guessed recipients or retry stale encrypted material unchanged.

Record reads and audit

Record writes and sharing

Providers and provider credentials

Gateways and routing

Gateway tokens

Logs and usage

Service Account access

Debugging order

  1. Check HTTP status and error.code.
  2. Read the specific reason in error.message.
  3. Confirm identity mode, account context and exact resource ID.
  4. Check RBAC and direct record or project access in the dashboard.
  5. Retry only temporary failures.
  6. Keep requestId when the same server failure continues.
Do not probe neighboring IDs after a not-found or authorization response. may intentionally hide whether an inaccessible resource exists.