HTTP Status Codes

This article lists common error codes from the PartsSource APIs. For troubleshooting tips, see the Troubleshooting section.

Error Response Format

When a request fails, PartsSource APIs return an error response following the RFC 7807 Problem Details standard. All error responses use the ApiProblemDetails schema:

{
  "type": "https://api.partssource.com/errors/not-found",
  "title": "Resource Not Found",
  "status": 404,
  "detail": "No order found with ID: 12345",
  "instance": "/orders/12345",
  "correlationId": "abc123-def456-ghi789",
  "errors": [
    "Order does not exist or has been deleted"
  ],
  "timestamp": "2025-01-10T14:30:00Z",
  "service": "customer-api"
}

Response Fields

Field	Type	Description
type	string	A URI reference identifying the problem type.
title	string	A short, human-readable summary of the problem.
status	integer	The HTTP status code.
detail	string	A human-readable explanation specific to this occurrence.
instance	string	A URI reference identifying the specific occurrence.
correlationId	string	Unique identifier for tracing the request. Include this when contacting support.
errors	array	List of specific error messages, useful for validation errors.
timestamp	string	ISO 8601 timestamp of when the error occurred.
service	string	The API service that generated the error.

Standard HTTP Error Statuses

HTTP Status	Name	Description
400	Bad Request	The server could not understand the request due to invalid syntax, invalid data types, or missing required fields. Check the errors array for specific validation issues.
401	Unauthorized	Authentication is required or the provided credentials are invalid. Verify your access token is valid and not expired.
403	Forbidden	You do not have permission to access this resource. Your token may lack the required scopes, or you're accessing a resource outside your authorized tenant.
404	Not Found	The requested resource does not exist. This may occur when referencing a deleted or non-existent order, user, or catalog item.
409	Conflict	The request conflicts with the current state of the resource. This may occur when creating a duplicate resource.
413	Payload Too Large	The request body exceeds the maximum allowed size.
429	Too Many Requests	You have exceeded the API rate limit. Wait before retrying. Check the Retry-After header for guidance.
500	Internal Server Error	An unexpected error occurred on the server. Include the correlationId when contacting support.
503	Service Unavailable	The service is temporarily unavailable. Retry with exponential backoff.