Changelog

Filter by:

June of 2025

  • New 403 status when creating reports
  • 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 the report cannot be generated from the main account, it must be done from a country-specific associated account. Check Create report for more information.

    Update

    Reports

    May of 2025

  • Update to the Preference Search Endpoint
  • 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.

    Update

    API Reference

  • Regularization of "external_reference" parameter in integrations
  • 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.

    Update

    API Reference

    April of 2025

  • New flow for URLs using HTTP protocol
  • Starting April 15, 2025, all requests that send URLs with the HTTP protocol in the back_urls field will be automatically cleaned by the API, resulting in empty entries in our database. This change is due to the risks associated with the HTTP protocol, which lacks encryption and allows access to sensitive data. The cleaning process will be gradual, so starting May 15, 2025, requests with HTTP URLs will be completely blocked. We invite all our integrators to review their configurations and switch to other accepted protocols.

    Update

    Security