Http Status Error Codes

This article lists common error codes from the PartsSource API's. For troubleshooting, see the Troubleshooting section. If there's an issue with your request, the response will include error details to help you fix it. All PartsSource API errors follow the same format. Below is an example error response for an incorrect parameter, such as when you try to access a resource without permission:

Example:

{
    error = "Company not found",
    message = $"No company found with ID: 123",
    code = "COMPANY_NOT_FOUND"
}

Standard HTTP error statuses

HTTP status	Explanation
400 Bad request	The server could not understand the request due to invalid syntax. This could happen, for example, due to the invalid data type and prohibited data duplication. Below you can find examples of more specific error messages related to some features:
403 Forbidden	You do not have access rights to the content which means that your request was unauthorized.
404 Not Found	The server cannot find the requested resource (probably it does not exist) even if the endpoint is valid. Servers may also send this response instead of 403 to hide the existence of a resource from an unauthorized client. This code may appear, for example, when you try to get details of the nonexistent/removed scenario, team, template, user, organization or app.
413 Payload Too Large	The request entity exceeded the limits set on the server. Below you can find examples of more specific error messages related to the Apps feature: Apps Failed to save image. Invalid upload Failed to save image. Image is too big Commit message is too big
429 Too many requests	You have exceeded the rate limit of API requests for your organization. Wait for one minute for the limit period to reset. Check the API rate limiting section for more information.
503 Service Unavailable	A dependency is currently unavailable.
304 Account Does Not Exist	This error appears when the account does not exist or it was not found.