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

3.229.0 release notes

about 1 hour ago by ReadMe API
  1. ✨ New features
    1. Added Avalara e-invoicing invoice-details support to POST /public-api/resources/users/v1.0/{user}/invoice-details and its response, as well as to User invoice-details responses on GET /public-api/resources/users/v1.0, POST /public-api/resources/users/v1.0, GET /public-api/resources/users/v1.0/{user}, PATCH /public-api/resources/users/v1.0/{user}, GET /public-api/resources/users/v1.1, POST /public-api/resources/users/v1.1, GET /public-api/resources/users/v1.1/{user}, and PATCH /public-api/resources/users/v1.1/{user}.
    2. Added the optional recipientCode and recipientCertifiedEmail fields to invoiceDetails on POST /public-api/resources/transactions/v1.0 and POST /public-api/actions/transactions/v1.0/{transaction}/issue-invoice. For Italian company invoice details when both fields are enabled, at least one of these fields must be supplied.
    3. Added the optional read-only fiscalization field to Partner invoice responses from GET /public-api/resources/partner-invoices/v1.0/{partnerInvoice}, POST /public-api/actions/partner-invoice/v1.0/{partnerInvoice}/issue-credit-note, and POST /public-api/actions/partner-invoice/v1.0/{partnerInvoice}/update-external-id. The field is present when the recorded invoice processor certified the document with a fiscal authority.
    4. Added the optional read-only issuer field to Roaming connection responses from GET /public-api/resources/roaming-connections/v2.0 and GET /public-api/resources/roaming-connections/v2.0/{roamingConnection}. It identifies the issuer configured for own tokens shared with the roaming partner; when omitted, the operator-level issuer applies.