Troubleshooting

This section describes most common mistakes that result in API-related problems, such as receiving Access denied or Not found errors. You can also refer to the HTTP status error codes for more details.

• Using HTTP instead of HTTPS in the URL

  Use HTTPS at the beginning of the URL in your request. This is required for security reasons.

• Using an incorrect environment

  If you have access to more than one PartsSource environment, ensure that you use the correct environment in the URL and that you use a valid authentication token generated for this specific environment.

• Using an incorrect endpoint

  Ensure there are no empty or white spaces in the endpoint URL and that there are no backslash symbols at the end of the URL after the endpoint name.

• Missing authentication details or using incorrect authentication details

  Ensure that you are using the correct authentication details. To make a successful request, you need to have the correct authentication token with the correct scopes assigned to it.

  Note that you need a separate token for each PartsSource environment.

• Missing access to the requested resource

  Ensure that scopes assigned to your authentication token correspond to the requested resource.

• Missing required parameters or using invalid or improperly formatted parameters

  Ensure each endpoint request includes the necessary parameters. Format query, path, and pagination parameters correctly. Begin the first query parameter with a question mark and separate others with an ampersand. Encode special characters in pagination parameters when they appear in URLs.

• Sending an invalid or improperly formatted request body

  The structure of the API request body must conform to the JSON schema standard. You can use JSON validators available on the internet to validate your request body before sending it.