Skip to main content

What it means

There is no resource with that id for the API key you used.

Common causes

  • The id is mistyped or was never returned by the API.
  • The object belongs to another partner. Other accounts’ objects look exactly like objects that do not exist.
  • The object exists in the other mode. A test key cannot read live data, nor the other way around.
  • The path itself is wrong.

What to do

  • Copy the id from a response of the API instead of building it by hand.
  • Check that the key you call with is the mode the object was created in.
  • Compare the path with the endpoint in the reference.
Every error response carries an error.request_id. Quote it if you write to support, and read Debugging your integration to look the call up yourself. All errors