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

3.267.0 release notes

about 1 hour ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Removed partnerInvoiceId from settlement report responses on GET /public-api/resources/partner-settlement-reports/v1.0, GET /public-api/resources/partner-settlement-reports/v1.0/{partnerSettlementReport}, GET /public-api/resources/partner-settlement-reports/v1.1, GET /public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport}, POST /public-api/actions/partner-settlement-report/v1.0/{partnerSettlementReport}/issue-partner-invoice, POST /public-api/actions/partner-settlement-report/v1.0/{partnerSettlementReport}/set-custom-fields, and POST /public-api/actions/partner-settlement-report/v1.0/{partnerSettlementReport}/update-external-id. Retrieve associated invoices through GET /public-api/resources/partner-invoices/v1.0 using filter[settlementReportId] instead.
    2. Changed email validation on POST /public-api/resources/partner-invites/v1.0 to require strict email validation. Addresses that previously passed validation may now be rejected.
  2. ✨ New features
    1. Added the experimental POST /public-api/actions/partner-expense/v1.0/{partnerExpense}/set-custom-fields endpoint to update an expense's customFields without changing its financial data. Omitted identifiers remain unchanged, and null clears a value; this experimental contract may change without a version bump.
    2. Added operatorId and optional customFields to expense items returned by GET /public-api/resources/partner-expenses/v1.2, along with custom-field filtering through filter[customFields.<identifier>]. Populated filters for unknown, unavailable, inaccessible, or non-filterable identifiers return 400; malformed values for usable identifiers return 422.
    3. Added expectedDocumentCount to the 202 response from POST /public-api/actions/partner-settlement-report/v1.0/{partnerSettlementReport}/issue-partner-invoice, indicating how many asynchronously generated documents to expect.
  3. 🔧 Improvements
    1. Changed deletion responses to return 409 Conflict with a message when tariff restrictions prevent deleting a partner, subscription plan, or user group on DELETE /public-api/resources/partners/v1.0/{partner}, DELETE /public-api/resources/partners/v2.0/{partner}, DELETE /public-api/resources/subscription-plans/v2.0/{subscriptionPlan}, and DELETE /public-api/resources/user-groups/v1.0/USERGROUP. Partner deletion on the v1.0 endpoint also returns 409 when blocked by roaming relationships.