Skip to main content

resource_not_found

HTTP 404, type invalid_request_error.

No resource with that identifier exists for your account.

Why it happened​

A resource belonging to another account also returns this, never a 403. A permission error would confirm that the identifier exists, which is information about someone else's account, so there is deliberately no way to tell the two apart from outside.

The usual causes are a mistyped or truncated identifier, an identifier of a different kind of object, or an object that belongs to another account.

How to fix it​

Check the identifier: that it is complete, and that it names the kind of object this request reads.

If you are certain the object exists, confirm the API key you are using belongs to the same account that created it.

Retrying: do not retry the same request. It will not find the resource. If you correct the identifier on a request that carries an Idempotency-Key, send the corrected request with a new key.

  • parameter_invalid -- an identifier that is empty or too long, on the endpoints that check its length