3.196.0 release notes
about 22 hours ago by ReadMe API
- ✨ New features
- Added the optional
paymentTermsfield to Operator responses onGET /public-api/resources/operators/v1.0andGET /public-api/resources/operators/v1.0/{operator}. When configured, this field returns the operator's payment terms value.
- Added the optional
- 🔧 Improvements
- Added explicit validation bounds to the
totalAmountandauthorizedAmountrequest fields onPOST /public-api/resources/transactions/v1.0andPATCH /public-api/resources/transactions/v1.0/{transaction}.totalAmountnow requires a minimum value of0.00, and both fields enforce a maximum of10000000000000.00. - The
name,city,address, and bank detail text fields on Operator and Partner responses now return the canonical locale-independent translation value. This ensures consistent output in multi-language configurations where these values are managed as translations rather than scalar columns. - The
nameandregion/statefilters on the Sub-Operator listing endpoint now match against translatable field values, and thesearchfilter on the Partner listing endpoint is now locale-aware. Results are more accurate in multi-language configurations where names and regions are stored as translations.
- Added explicit validation bounds to the