ORDER_NOT_FOUND

Where it comes from: GET /v1/orders/{provider}/{id} (mapped from deBridge UNKNOWN_ORDER).

Causes#

• The id was never an order on that provider.
• The wrong provider was used for the id.

How to fix#

• Use the provider of the quote you executed and the id described in Order tracking.
• Right after broadcasting, most providers return pending or unknown until they index the source transaction — keep polling.

Example response#

{
  "error": {
    "code": "ORDER_NOT_FOUND",
    "message": "deBridge: order not found",
    "requestId": "0d5e1f6a-3b2c-4d1e-8f9a-7b6c5d4e3f21",
    "docsUrl": "https://docs.layerhop.com/errors/ORDER_NOT_FOUND"
  }
}

See Error handling & retries for a retry strategy, and the error catalog for every code.