When you interact with the PagSeguro Payout API, responses include HTTP status codes that indicate whether the request was successful, failed, or encountered an issue. Understanding these codes helps you handle errors gracefully and troubleshoot issues quickly.
Status Code Reference
The table below outlines all possible HTTP status codes returned by the Payout API and what they mean for your request.
| Code | Name | Description |
|---|---|---|
204 | No Content | The payout request was accepted and will be processed. No response body is returned. |
404 | Not Found | The specified resource (e.g. batch reference, report date) was not found. Check for typos or invalid paths. |
409 | Conflict | A payout with the same reference was already submitted. Use a unique reference to avoid duplication. |
413 | Payload Too Large | The request body exceeds the server’s allowed size limit. Try reducing the number of payout items. |
422 | Unprocessable Content | The request was syntactically correct, but contained invalid or inconsistent business logic. |
429 | Too Many Requests | You have hit the rate limit for the API. Wait before retrying or implement backoff. |
500 | Internal Server Error | An unexpected error occurred on the server. If persistent, contact PagSeguro support. |
504 | Gateway Timeout | The server did not receive a timely response from an upstream system. Retry later or contact support. |