resource_not_found

What it means

The id in the path does not resolve to a resource this key's project can see. Ids are project-scoped: another project's resource answers this same 404, deliberately.

Common causes

• The resource was deleted.
• The id belongs to a different project than the key.
• A mistyped or stale id.

How to fix it

List the collection first and use ids from the response. Do not treat this as proof the id does not exist anywhere — only that it does not exist for this key.

Should you retry?

No.

The response shape

Every /v1 error is an RFC 9457 application/problem+json document: type links to this page, code is the stable value to branch on (never parse title or detail), and request_id identifies the request to support. Validation failures add an errors array of per-field JSON pointers.

API overview · API reference · All error codes:

• missing_credentials — HTTP 401, Missing credentials
• invalid_api_key — HTTP 401, Invalid API key
• invalid_token — HTTP 401, Invalid access token
• unsupported_credential_type — HTTP 403, Credential type not usable on this surface
• insufficient_scope — HTTP 403, Insufficient scope
• feature_not_enabled — HTTP 403, Feature not enabled on this plan
• validation_failed — HTTP 400, Request validation failed
• rate_limited — HTTP 429, Rate limit exceeded
• quota_exhausted — HTTP 429, Plan quota exhausted
• idempotency_key_reused — HTTP 422, Idempotency-Key reused with a different request
• idempotency_in_progress — HTTP 409, A request with this Idempotency-Key is still in progress
• internal_error — HTTP 500, Internal server error