Skip to main content
HTTP status: 404 · Title: “Not Found”

​
When it fires

A request for a specific resource found nothing the caller is allowed to see. Returned by GET /v1/trades/{id}, POST /v1/trades/{id}/confirm, GET /v1/traces/{correlationId}, /v1/markets/{id}/disputes and POST /v1/webhooks/events/{eventId}/redeliver, among others. This is the generic 404. Some resources have their own code where the distinction helps, such as MARKET_NOT_FOUND.

​
Why it happens

  • The id is wrong (a typo or cross-environment confusion).
  • The resource exists but belongs to another account. The API returns 404 rather than 403 deliberately, so nobody can probe for resources they don’t own.
  • The resource was deleted.

​
How to fix

  • Re-check the id (case, hyphens, environment).
  • If the resource should exist but you can’t see it, confirm you are authenticated as its owner.
A request to a path that is not an API endpoint at all returns a 404 with code: "ROUTE_NOT_FOUND" and type: "about:blank", not this code. Check the path against the Endpoint reference.