Status Codes

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

HTTP Status Code

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 (e.g. Promise Mode)
  • 204 No Content: Request processed successfully; no response body (used for updates and deletes)
  • 299 Warning – Request processed, but with a warning that may affect subsequent operations

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
  • 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; “Retry-After” header may indicate when to retry

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.

© 2025 Priority Technology Holdings LLC. All rights reserved.