When working with APIs, it’s important to know how the system responds to your requests. HTTP response codes provide clear, standardized feedback that helps developers understand outcomes, handle failures gracefully, and build more resilient integrations.

This section explains the most common codes you may encounter while using PCE APIs, along with guidance on how to interpret and act on them.

HTTP Response Codes

Status codes indicate the outcome of your API request. They help you quickly understand whether the request was successful, needs correction, or failed due to an unexpected issue. Familiarity with these codes allows you to build more reliable integrations and handle responses efficiently.

PCE uses conventional HTTP response codes to indicate the success or failure of an API request to help you diagnose and resolve errors efficiently.

Code	Description
`2xx` range indicates success	Common codes include: `200 OK`: Request completed successfully. `201 Created`: Request successful. Create API's returns `URL` in`Location` header with object ID `202 Accepted`: Request accepted for processing; may not be acted upon immediately `204 No Content`: Request processed successfully; no response body
`4xx`range indicates an error that failed based on the information provided.**	Common codes include: `400 Bad Request` : The request was not accepted due to a missing required parameter or a syntax error. `401 Unauthorized`: Authentication failed (invalid or missing token) `404 Not Found`: The requested resource does not exist `405 Method Not Allowed`: HTTP method not supported for this endpoint `406 Not Acceptable`: The server cannot generate a response that matches the formats specified in the request's Accept header `415 Unsupported Media Type`: Request body format not supported `422 Unprocessable Entity`: Well-formed request but semantic or business validation failed `429 Too Many Requests`: Rate limit exceeded
5xx incates an error with PCE services	Common codes include: `500 Internal Server Error`: PCE server error. Retry request. If it persists, contact Priority support. `503 Service Unavailable`: Service is temporarily unavailable. Typically due to maintainence. Please see attached JSON payload for details or try again later.

Code

Description

2xx range indicates success

Common codes include:

200 OK: Request completed successfully.
201 Created: Request successful. Create API's returns URL inLocation header with object ID
202 Accepted: Request accepted for processing; may not be acted upon immediately
204 No Content: Request processed successfully; no response body

4xxrange indicates an error that failed based on the information provided.**

Common codes include:

400 Bad Request : The request was not accepted due to a missing required parameter or a syntax error.
401 Unauthorized: Authentication failed (invalid or missing token)
404 Not Found: The requested resource does not exist

405 Method Not Allowed: HTTP method not supported for this endpoint
406 Not Acceptable: The server cannot generate a response that matches the formats specified in the request's Accept header
415 Unsupported Media Type: Request body format not supported
422 Unprocessable Entity: Well-formed request but semantic or business validation failed
429 Too Many Requests: Rate limit exceeded

5xx incates an error with PCE services

Common codes include:

500 Internal Server Error: PCE server error. Retry request. If it persists, contact Priority support.
503 Service Unavailable: Service is temporarily unavailable. Typically due to maintainence. Please see attached JSON payload for details or try again later.