Common error messages for partner integrations

The following table describes the errors you might encounter, and their common fixes:

Error Code	Description	Common fix
400	Incorrect request. The server received a request it couldn’t understand. Often caused by typos, invalid characters, or improper syntax.	Check the request for errors and try again.
401	Unauthorized. The request lacked the valid authentication required. Often caused if the wrong authentication type is given with the request.	If you’re trying to call a public API, make sure that you’re providing a valid API Key and BUID. If you’re trying to call a private API, make sure that you have a valid access token that has access to your customer’s BUID.
403	Forbidden. Often caused if you or your customer don’t have the required access. This is typically due to admin permissions.	Check if the application is enabled and that your customer has access to the domain as well as admin status.<br.> Display the following message to the end user: “You need a paid Trustpilot plan to use this integration. Contact Trustpilot here to get access.”
404	The server couldn’t find what you asked for. Often caused by an incorrect URL (a base URL that isn’t api.trustpilot.com or invitations-api.trustpilot.com) or incorrect PartnerID	Check your URL and PartnerID for errors.
415	Unsupported media type.	Make sure that you’ve used the correct Content-Type in your header.
500	Server error.	Try again in 5-15 minutes.
501	Request not supported. There’s no implementation for your request on the server yet.	If there’s a specific feature that you want to use, ask your Customer Success Manager when implementation on the server is expected.