Skip to content

Not found

HTTP 404not_found

When the API answers 404 not_found, and how to fix it.

Version v1.1, updated

The type field of every not_found response links to this page.

On this page

No record with this id exists for this key. An id of another company answers the same way, as if it did not exist.

At a glance

  • Status: 404 Not Found

  • Code: not_found

  • Retry: No. Fix the cause first: the same request gets the same answer.

Causes and fixes

Likely cause

How to fix it

The id is mistyped or cut short.

Copy the id from a list or from the answer of the create.

The id is the id of your own system, not the BIRP id.

Find the record by its external id, such as GET /v1/products?source=woocommerce&external_id=1042.

The record was created with the key of another company.

Use a key of the company the record was created for. Each key sees the records of its own company only.

The path names another resource than the id, such as an order id on /v1/invoices/{id}.

Check that the id and the resource of the path match.

Example

404 not_foundJSON
{
  "code": "not_found",
  "detail": "The requested resource does not exist.",
  "instance": "/v1/categories/00000000-0000-4000-8000-000000000021",
  "request_id": "a1b2c3d4-0000-4000-8000-0000000000ee",
  "status": 404,
  "title": "Not found",
  "type": "https://birp.io/developers/errors/not_found"
}

Related

  • references-and-external-ids
  • route-not-found
  • errors-overview