HTTP Status CodesΒΆ


The PB Shipping APIs use the following HTTP status codes to indicate the success or failure of an API request. If a request fails, an error code and message are also returned. To troubleshoot errors, see Troubleshooting. To view the status of the APIs, see the Pitney Bowes API Status Page.

Code

Message

Additional Information

200

OK

The request is successful.

201

Created

The new resource is created.

400

Bad Request

Possible causes include a missing parameter, missing value, invalid structure, or malformed request.

401

Unauthorized

Possible causes include an expired or invalid access token.

403

Forbidden

Possible causes include the account is not enabled for the operation.

404

Not Found

The resource does not exist or is temporarily unavailable.

405

Method Not Allowed

The HTTP method specified in the request (e.g., POST, GET, DELETE) is not allowed for this resource.

500

Internal Server Error

There has been an error on the Pitney Bowes servers.

IMPORTANT: If you receive this error when creating a shipment, see Troubleshoot the 500 Internal Server Error.

If this error occurred for a different API call, try the call again. If the problem persists, please contact Support.

503

Service Unavailable

Possible cause can be an unplanned maintenance window. Try the call again. If the problem persists, please contact Support.