resource_missing API Origin: Application & API Last updated 13 Oct 2026

API Error: No such object / resource_missing (resource not found by ID)

The endpoint exists, but the ID you passed — in the URL or as a reference in the body — doesn’t match any record the caller can see.

Exact message you may see No such customerNo such priceNo such payment_intentResource not foundReferenced resource not found
Explore the map of this error Full error map →
Seen on: REST API

Meaning

APIs return this when a lookup by ID fails: Stripe says “No such customer: 'cus_123'” (code resource_missing), others “Resource not found” or “Referenced object does not exist”. It covers both the record you’re fetching and records you reference from a create/update request (a customer_id, price_id, parent_id).

The record may be deleted, belong to another account or tenant, or exist in a different environment — test vs live, staging vs production — which is the single most common reason.

Common causes

  • Wrong or stale ID (deleted, typo, truncated)
  • ID from another environment (test vs live, staging vs prod)
  • ID from another account/tenant/connected account
  • Referenced object deleted after it was saved locally
  • Caller lacks permission and the API hides the object as “not found”

⚡ Quick fix

  1. Look the ID up directly with the same credentials
  2. Check the key/environment matches where the ID was created
  3. Re-sync or re-create the referenced object if it was deleted

Detailed fix by platform

REST API

  1. bash
    # fetch the object with the SAME key the failing request uses
curl https://api.stripe.com/v1/customers/cus_123 -u "$STRIPE_KEY:"

How to diagnose

  1. Lookup — Does GET /resource/{id} succeed with the same key?
  2. Environment — Test or live key? Which project/tenant?
  3. History — Deleted? Check audit/event logs

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Application & API. Errors that are often confused with or caused by this one (click to open):

404 — HTTP 404 Not Found (HTTP)404410 — HTTP 410 Gone (HTTP)410Cannot return null for non-nullable field — GraphQL: Cannot return null for non-nullable field Query.user (API)Cannot return null fo…concurrent_requests_limit — API Error: Too many concurrent requests (concurrency limit reached) (API)concurrent_requests_l…CORS — CORS Error: No 'Access-Control-Allow-Origin' header is present (API)CORSinvalid_id — API Error: Invalid ID format (not a valid UUID / malformed identifier) (API)invalid_idjob not found — API Error: Job / operation not found or expired (async task ID unknown) (API)job not foundtest/live mismatch — API Error: a similar object exists in test mode, but a live mode key was used (API)test/live mismatchresource_…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.