HomeGuidesAPI ReferenceChangelog
Terms of Use
Changelog
Terms of Use
Back to All

3.262.0 release notes

about 1 hour ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Changed validation to reject deleted roaming connections in connectionId on POST /public-api/resources/roaming-emsps/v1.0 and platformId on POST /public-api/resources/roaming-providers/v2.0. Consumers must use an existing, non-deleted connection.
  2. ✨ New features
    1. Added the optional, read-only roamingId field to responses from GET /public-api/resources/roaming-cpos/v1.0, GET and PATCH /public-api/resources/roaming-cpos/v1.0/{roamingCpo}, GET and POST /public-api/resources/roaming-emsps/v1.0, GET and PATCH /public-api/resources/roaming-emsps/v1.0/{roamingEmsp}, GET and POST /public-api/resources/roaming-providers/v2.0, and GET and PATCH /public-api/resources/roaming-providers/v2.0/{roamingProvider}. It identifies the roaming party using its Hubject ID or OCPI country code and party ID joined with *, and is omitted when unavailable.
    2. Added the optional filter[paymentTerminalIntegrationId] and filter[paymentProcessorId] query parameters to GET /public-api/resources/transactions/v1.0. Each accepts an array of integer IDs to filter transactions by payment terminal integration or payment processor; blank entries are ignored.
  3. 🔧 Improvements
    1. Expanded supported language values with es-CO (Spanish — Colombia) for language on partner invites and notifications.billing.settlementReportLanguage on partners. This affects GET and POST /public-api/resources/partner-invites/v2.0, GET and PATCH /public-api/resources/partner-invites/v2.0/{partnerInvite}, GET and POST /public-api/resources/partners/v2.0, GET and PATCH /public-api/resources/partners/v2.0/{partner}, and the response from POST /public-api/actions/partner/v1.0/{partner}/set-custom-fields.
    2. Changed roaming listings to exclude records associated with deleted connections on GET /public-api/resources/roaming-cpos/v1.0, GET /public-api/resources/roaming-operators/v2.0, GET /public-api/resources/roaming-emsps/v1.0, GET /public-api/resources/roaming-providers/v2.0, and GET /public-api/resources/roaming-tariffs/v2.0. Reading or updating an affected roaming tariff through GET or PATCH /public-api/resources/roaming-tariffs/v2.0/{roamingTariff} now returns 404 Not Found.
    3. Changed tariff selection on GET /public-api/resources/tariffs/v1.0 when both filter[tariffGroupId] and filter[userId] are supplied to select the applicable tariff before checking API visibility, tariff type, and custom field filters. If that tariff does not match, the response is empty rather than selecting an alternative tariff.
    4. Changed filter[userId] handling for tariff-group selection on GET /public-api/resources/tariffs/v1.0: malformed or unknown user IDs now return an empty collection. An empty value or the literal string null selects the tariff without a user-specific context.
    5. Changed name uniqueness validation on POST /public-api/resources/user-groups/v1.0 and PATCH /public-api/resources/user-groups/v1.0/USERGROUP to check within the group's operator and partner context. Names can be reused across operators, and groups without a partner are checked separately from partner-associated groups.
    6. Changed integrationId validation on POST /public-api/resources/flexibility-assets/v1.0 and PATCH /public-api/resources/flexibility-assets/v1.0/{flexibilityAsset} to verify that the referenced integration is a flexibility integration, rather than accepting an ID belonging to another integration type.
    7. Expanded subscription termination through POST /public-api/actions/users/v1.0/{user}/terminate-subscription to support the current subscription while it is awaiting renewal within the renewal grace period, instead of returning 404 solely because its billing period has ended.
    8. Added a 409 Conflict response when finalizing a payment card through POST /public-api/resources/users/v1.0/{user}/payment-methods if the card is already registered to another user and the payment processor restricts cards to a single user. Retrying the same card does not resolve the conflict; a different card is required.