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

3.246.0 release notes

about 2 hours ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Changed the default ordering for GET /public-api/resources/sub-operators/v2.0 from businessName to the English (en) sub-operator name. Custom sorting is no longer supported.
    2. Changed the filter[name] and filter[region] filters on GET /public-api/resources/sub-operators/v2.0 to match only English (en) translations, without fallback to another locale or the original stored value.
    3. Made email-address validation stricter for PUT /public-api/resources/contact-details/v2.0 and POST /public-api/resources/partner-invites/v2.0. Requests containing addresses that were previously accepted with RFC warnings may now receive a validation error.
  2. ✨ New features
    1. Added locale-specific translatedName, translatedAddress, translatedCity, and translatedRegion properties for Sub-operators on POST /public-api/resources/sub-operators/v2.0 and PATCH /public-api/resources/sub-operators/v2.0/{subOperator}. Submitted translations replace the full locale set for the affected property; translatedName requires an English (en) entry.
    2. Added translatedName, translatedAddress, translatedCity, and translatedRegion to Sub-operator responses from GET /public-api/resources/sub-operators/v2.0, POST /public-api/resources/sub-operators/v2.0, GET /public-api/resources/sub-operators/v2.0/{subOperator}, and PATCH /public-api/resources/sub-operators/v2.0/{subOperator}.
    3. Added optional card-enrichment properties under paymentMethod on POST /public-api/resources/transactions/v1.0 and PATCH /public-api/resources/transactions/v1.0/{transaction}: cardType, bin, fingerprint, acquirerName, issuerName, and issuerCode.
  3. 🔧 Improvements
    1. Made POST /public-api/resources/sub-operators/v2.0 accept translatedName as an alternative to the legacy name property when creating a Sub-operator.
  4. 🗑️ Deprecations
    1. Deprecated the Sub-operator name, address, city, and region properties on POST /public-api/resources/sub-operators/v2.0, PATCH /public-api/resources/sub-operators/v2.0/{subOperator}, and their responses. Use translatedName, translatedAddress, translatedCity, and translatedRegion instead; each legacy property cannot be sent together with its translated replacement.