Handling Errors in Production

You are advised to have a timeout for all headless API requests. Please handle this in your app integration.

For critical connectivity issues, please refer to https://status.lcly.co/ for updates. The API (v2 / Headless, Cart and Marketing) component will report any ongoing issues.

Responses

Verbose

{
	"success": false,
	"msg": "There is a difference between the requested (3.75) and calculated (4.12) tax for some items. AvaTax calculated an amount higher than the TaxOverride amount provided for an SST transaction. The higher amount will be reported.",
	"error_code": 1335
}

There are several msg payloads which contain verbose information about the reason for the failure. Each error message is accompanied by a specific error_code (see the table below).

Fatal

{
	"success": false,
	"msg": "App server error. Please contact the administrator. - lookup: 1724262168",
	"error_code": 1000
}

Unexpected, fatal errors will occur if there is a problem with the data payload that locally is unable to process, but cannot reply with specific detail about the root cause. These errors are logged securely at Locally for authorized review. We also encourage you to file a ticket with our customer support team at support@locally.com to report any you find.

The msg field for these errors will always be prefixed with App server error with an error_code of 1000.

General Errors

Bulk Order Validation Errors