not_found

HTTP status: 404

The resource identified by the path or request body does not exist, or it exists but is not accessible with the current token.

Why this happens

• The ID in the URL path was copied incorrectly or belongs to a resource in the other mode (test vs. live).
• You are looking up a resource that was created in test mode using a live token, or vice versa.
• The resource was deleted and no longer exists.
• The resource ID belongs to a different account than the token used for authentication.

What to do

1. Verify the ID is correct — compare against the id field in a recent successful response.
2. Check the livemode field on recent responses to confirm you are querying the right mode. A resource created in test mode returns not_found when queried with a live token.
3. If the resource was recently deleted, that is expected behavior — 404 is the correct response for deleted resources.
4. If you believe the resource exists and should be accessible, contact [email protected] with the resource ID and your request_id.

Example response

{
  "type": "https://zyins.isaapi.com/errors/not-found",
  "title": "Resource not found",
  "status": 404,
  "detail": "Case 'case_01HZK2N5GQR9T8X4B6FJW3Y1AS' was not found. Verify the ID and that the token mode matches the resource's livemode.",
  "code": "not_found",
  "param": null,
  "request_id": "req_01HZK2N5GQR9T8X4B6FJW3Y1AS"
}

SDK exceptions

See also

• Error catalog
• Test mode guide