Reconciliation Report Errors
The following error codes and messages appear in REST responses when an error prevents completion of the request.
Error Code | Description |
|---|---|
MISSING_AUTHENTICATION_HEADERS | The request did not contain the required headers for authentication. The request was rejected. Corrective action: Add authentication headers. |
UNAUTHENTICATED_API_CALL | The request was rejected due to an authentication issue. Corrective action: Check the status of your account in the 'Account Details' page of the Client Portal. |
UNAUTHENTICATED_API_CALL | The API received a request, but the signature did not match. The request was rejected. Corrective action: (1) Remove all whitespace that is not inside a string. (2) Remove trailing zeroes and decimal points, or wrap numbers in a string. |
ERROR_REPORTS_RATE_LIMIT_EXCEEDED | The request tried to retrieve a partitioned report, but the number of requests exceeded the allowed rate limit. The request was rejected. Corrective action: Reduce your request frequency and retry using exponential backoff. |
ERROR_NO_REPORT_EXISTS_FOR_MERCHANT | The request tried to retrieve a report, but no report exists for the specified merchant. The request was rejected. Corrective action: Verify that reporting is enabled for the merchant and that you are using the correct merchant credentials. |
ERROR_REPORT_TYPE_DOES_NOT_EXIST_FOR_MERCHANT | The request tried to retrieve a report of the specified type, but that report type does not exist for the merchant. The request was rejected. Corrective action: Check the report_name path parameter and use a report type that is enabled for the merchant. |
ERROR_INVALID_REPORT_DATE | The request tried to retrieve a report for the given date, but the date was not valid. The request was rejected. Corrective action: Provide the date as zero-padded yyyy, mm, and dd path parameters (for example, 2026/06/18). |
ERROR_REPORT_DOES_NOT_EXIST_FOR_DATE | The request tried to retrieve a report for the requested date, but no report exists for that date. The request was rejected. Corrective action: Verify the date is correct and that the merchant had activity on that date. |
ERROR_INVALID_REPORT_PAGE | The request tried to retrieve a specific page of the report, but the page number was invalid or out of range. The request was rejected. Corrective action: Request page 1 first, then request pages up to the total_pages value returned in the response. |
ERROR_GET_RECON_PARTITIONED_REPORTS | The request tried to retrieve the partitioned report, but the report could not be retrieved. The request was rejected. Corrective action: Verify the request parameters and try again; if the problem persists, contact Rapyd support. |