not-foundCopy Anchor Link

HTTP 404. Either no endpoint matches the method and path you requested, or the order, product or test order you named is not on this connection.

{
  "type": "https://developers.supliful.com/errors/not-found",
  "title": "Resource not found",
  "status": 404,
  "detail": "No route matches GET /v1/order.",
  "instance": "/v1/order"
}

The detail names the method and path we received, which is usually enough to spot the problem by comparing it with what you meant to send.

Two causesCopy Anchor Link

• No such route. A routing failure is returned before any authentication or lookup happens, so you see it whether or not you sent a valid key. The detail names the method and path we received.
• No such resource. For GET /v1/orders/{orderId}, GET /v1/products/{id} and the cancel and sandbox endpoints, the id is not one this connection can see. An order of another connection answers the same way as one that never existed. A test order also answers 404 once its two hours are up.

How to fix itCopy Anchor Link

• For a resource, check the id and the key. An order is found by Supliful's id or your externalOrderId, and only with a key of the connection that placed it.
• Check the version prefix. Every endpoint is under /v1. A path without it will never match.
• Check the method. The same path can exist for one method and not another; detail shows the method we saw.
• Check for a trailing slash or a doubled segment. //v1/me and /v1//me are different paths from /v1/me.
• Compare against the API Reference. It is generated from the served routes, so anything listed there exists and anything absent does not.

If you are calling an endpoint you were told about but cannot find in the reference, it has not shipped yet. Ask us at help@supliful.com rather than building against it.

Retry behaviourCopy Anchor Link

Terminal. Retrying an unmatched path cannot start matching, and an id this connection cannot see will not appear on a retry.