Contract v1 · generated reference

Getting started

Keep identity, App Check, data and provider mode inside the same sandbox boundary.

Use the assigned sandbox Firebase project or the local Emulator Suite. Do not mix environment identifiers.
Initialize Firebase Auth and App Check from the approved client configuration; keep server credentials off the client.
Choose an operation from the generated reference and verify its actor, transport and resource boundary.
Send required idempotency keys and version preconditions exactly as documented in retry safety.
Exercise denial, conflict, expiry, rate-limit and unavailable paths before treating the integration as ready.

Before the first request

Confirm the Auth token and App Check token came from the same sandbox project.
Use placeholder identities and non-sensitive fixtures.
Log only the stable operation id, environment, release and a privacy-safe correlation id.
Stop after bounded retries and consult service status.

Common integration contract

Sandbox and Production are isolated

Run examples only in a governed sandbox or local emulator. Sandbox identities, App Check tokens, payment fixtures and data do not grant Production access. The typed ports do not ratify a public numeric quota; enforcement may be stricter. Honor RATE_LIMITED and the server's retry-after value.

Authentication and authorization

Firebase Auth proves identity. App Check proves the approved app where a callable requires it. Roles, organization membership, requester identity and resource ownership are derived and rechecked by the server.

Authentication guide

Errors and recovery

Stable error codes distinguish validation, denial, conflict, expiry, authority pending, rate limiting and temporary unavailability. Never infer success from an HTTP redirect or a browser state.

Error catalogue

Idempotency, concurrency and retry

Reuse an idempotency key only for an identical retry. A new intent needs a new key. Preserve version preconditions and reload after a conflict.

Retry guidance

Changes and escalation

Check compatibility before adopting a new contract version. Review the changelog, service status and support guidance before retrying a persistent failure.

Changelog Service status Developer support

Common failure families
Family	Client decision
Authentication / authorization	Refresh or step up only when instructed; do not retry a denial unchanged.
Validation / conflict / expiry	Correct or reload state, then obtain confirmation for a new intent.
Rate limited / unavailable	Honor retry-after and use bounded backoff; inspect service status.
Unknown / server	Fail closed and escalate with a privacy-safe correlation id.

Executable network examples are published only when the exact wire schema is producer-proven. Check the selected operation's example-availability status; an unresolved schema is a release blocker, not permission to guess.

Verified examples and local-only recovery snippets