Error Codes International API

The PagSeguro International API uses standard HTTP status codes to indicate the success or failure of an API request. This page outlines the types of errors you may encounter, how to interpret them, and how to troubleshoot.

HTTP Status Codes

The possible HTTP status code return by the International API are listed and described in the following table.

Response Formats

400 Bad Request

Returned when one or more fields are invalid. The API returns an array of error objects so you can validate all issues at once.

{
  "errors": [
    {
      "message": "Value is required and can't be empty",
      "location": "body.payer.email"
    },
    {
      "message": "Invalid type given. String expected",
      "location": "body.payer.email"
    }
  ]
}

401 Unauthorized

Returned when the request is not authenticated. The response body is empty:

{}

422 Unprocessable Entity

Returned for semantically incorrect requests such as business logic violations.

{
  "error": "charge_payment_method_not_enabled"
}

Error List

400 Bad Request

422 Error List

When the server understands the request but cannot process it due to business rule violations, it returns a 422 Unprocessable Entity error with the following format:

{
  "error": "charge_payment_method_not_enabled"
}

Common 422 Errors