New possible request errors have been included that may be returned by the Orders API for the Checkout API, as follows:

• "order_invalid_sponsor_id"
• "invalid_header_value"
• "order_refund_already_in_process"
• "invalid_credentials"
  
  For more details about these and other possible errors, as well as how to fix them, please check the Possible errors documentation.

The 403 Forbidden status code was added as a possible response when creating a release report. This error includes the message "operation not allowed" and means that the report cannot be generated from the company's general account. Instead, it must be generated from the account associated with the relevant country—that is, through the account of the country for which the report is to be generated. Check Create report for more information.

Starting from 05/07/2025, we will implement a change to the preference search endpoint: only those created within the last 90 days will be considered. Older preferences must be accessed using their ID through the corresponding endpoint. This change will be applied progressively and will be completed by 05/19/2025. For more details, visit the news.

Regularization of "external_reference" parameter in integrations

To avoid issues with transactions, update the "external_reference" parameter sent through the preferences and payments API before 10/10/2025. This field must be a maximum of 64 characters and may only contain numbers, letters, hyphens (-), and underscores (_). Special characters such as ([ ], (), ", @) are not allowed. See the documentation for more information.