Error codes and reasons

Wolt's APIs utilize standard HTTP response codes to communicate the outcome of an API request, distinguishing between success and failure.

The following code ranges are applicable to all endpoints:

  • 2xx: Operation was a success.
  • 4xx: Operation failed due to a client error, trying again would result in same outcome.
  • 5xx: Operation failed due to a temporary Wolt failure, try again later.

Below is a list of the most error codes and their reasons that you may encounter when using Wolt's APIs for integrations.

Order API error codes

400 Bad Request

Indicates that the server cannot or will not process the request due to something that is perceived to be a client error. For example a malformed request syntax, an invalid request message framing, or a deceptive request routing.

  • Check that you're using the correct API.
  • Ensure the request payload matches the schema for the used API.
  • If you're using Amazon's servers it could be a CloudFront issue. Can be solved by sending the request from the partners own server instead of using Amazon’s server.

401 Unauthorized

Indicates that the request has not been applied because it lacks valid authentication credentials for the target resource.

  • Make sure bearer token is present in the request's Authorization header.
  • Ensure the access token has not been expired.
  • Check which environment is used. Development environment uses different hostname than production.
  • Check that the APIs you're trying to use have been activated for the venue. Contact your Wolt account manager or technical account manager to activate the APIs.

Indicates that the server cannot or will not process the request due to something that is perceived to be a client error. For example a malformed request syntax, an invalid request message framing, or a deceptive request routing.

  • Check that you're using the correct API.
  • Ensure the request payload matches the schema for the used API.

Indicates that the request has not been applied because it lacks valid authentication credentials for the target resource.

  • Make sure bearer token is present in the request's Authorization header.
  • Ensure the access token has not been expired.
  • Check that you are using the correct venue ID.
  • Check which environment is used. Development environment uses different hostname than production.
  • Check that the APIs you're trying to use have been activated for the venue. Contact your Wolt account manager or technical account manager to activate the APIs.

Indicates that the server has not found anything matching the request URI.

  • Check if the correct API method has been used.

Item Update endpoint of Menu API error codes

400 Bad Request

Indicates that the server cannot or will not process the request due to something that is perceived to be a client error. For example a malformed request syntax, an invalid request message framing, or a deceptive request routing.

  • Check that you're using the correct API.
  • Ensure the request payload matches the schema for the used API.
  • Check that the items all have a POS ID, GTIN, or Merchant SKU.
  • Check if the correct mapping is being used i.e. the payload has “sku” and the item in our menu editor also has a “sku”.

401 Unauthorized

Indicates that the request has not been applied because it lacks valid authentication credentials for the target resource.

  • Make sure bearer token is present in the request's Authorization header.
  • Ensure the access token has not been expired.
  • Check that you are using the correct venue ID.
  • Check which environment is used. Development environment uses different hostname than production.
  • Check that the APIs you're trying to use have been activated for the venue. Contact your Wolt account manager or technical account manager to activate the APIs.

404 Not Found

Indicates that the server has not found anything matching the request URI.

  • Check if the correct API method has been used.

429 Too Many Requests

Indicates that the user has sent too many requests in a given amount of time. This is a rate limiting error.

Inventory Update endpoint of Menu API error codes

400 Bad Request

Indicates that the server cannot or will not process the request due to something that is perceived to be a client error. For example a malformed request syntax, an invalid request message framing, or a deceptive request routing.

  • Check that you're using the correct API.
  • Ensure the request payload matches the schema for the used API.
  • Check that the items all have a POS ID, GTIN, or Merchant SKU.
  • Check if the correct mapping is being used i.e. the payload has “sku” and the item in our menu editor also has a “sku”.

401 Unauthorized

Indicates that the request has not been applied because it lacks valid authentication credentials for the target resource.

  • Make sure bearer token is present in the request's Authorization header.
  • Ensure the access token has not been expired.
  • Check that you are using the correct venue ID.
  • Check which environment is used. Development environment uses different hostname than production.
  • Check that the APIs you're trying to use have been activated for the venue. Contact your Wolt account manager or technical account manager to activate the APIs.

404 Not Found

Indicates that the server has not found anything matching the request URI.

  • Check if the correct API method has been used.

409 Conflict

Indicates that an inventory update has already been sent and that everything worked but then a duplicate request was sent with the exact same payload to us with no change in the stock or in the data. The same request was sent twice to us and the first request was received and it was processed.

If the merchants wants to send again the same catalog update it can be done 24 hours later and they will get a 202 Accepted response. This is not related to the rate limit.

429 Too Many Requests

Indicates that the user has sent too many requests in a given amount of time. This is a rate limiting error.