2025 R2

This release went live on 2025-05-09

Welcome to our latest REST API release

The 2025 R2 release was busy! We're happy to announce the addition of many new endpoints as well as other improvements and functionality to enhance your developer experience.

Sage Intacct encourages your feedback, which you can provide using the Feedback tab on the right side of the page.

New endpoints

This release includes new endpoints in many applications.

Accounts Payable

Accounts Receivable

Cash Management

Construction

Construction Forecasting

Contracts and Revenue Management

Expense Tracking

Fixed Assets Management

General Ledger

Inventory Control

Order Entry

Project and Resource Management

Purchasing

Other updates

Batch requests

You can process multiple records (batch) for a single REST API object in one request. To learn more about batch requests, see Batch requests.

Bulk request service is now in General Availability (GA)

Now you can use the bulk service to process large volumes of data for improved efficiency. The bulk service enables scalability by handling large-scale non-blocking data processing.

To learn more about this service, see Bulk requests.

Outbound webhooks (General availability)

Last release we announced a new option for Platform trigger post requests. The feature offers reliable and consistent webhook delivery and automatic retries for handling delivery failures. We're pleased to announce that the feature is now generally available. To learn more about it, see Outbound webhooks

Platform Trigger queue event services (Early Adopter)

A new Platform Trigger type, Event queue, allows users to queue payloads in storage. After the trigger is created, you can use Platform Trigger queue event services to retrieve a count of events, retrieve batch messages, and also post acknowledgements of trigger events using HTTP methods and cURL commands.

To learn how to set up the new trigger, see Platform Event Queue Trigger--Early Adopter. Also refer to Platform Trigger queue event services (Early Adopter) for technical details on setting up calls.

Planned improvements

The following enhancements are planned for a future release.

  • The Purchasing document-history object does not currently support queries on the convertedFrom and convertedTo fields and their properties. Including these fields and their properties in a query request will result in an error message about an invalid field. Queries on these fields will be supported in an upcoming release.
  • Accounts Payable recurring-bill-line object - the response code for a successful PATCH operation will be changed from 201 Created to 200 OK .
  • When you issue a POST request to create an Inventory Control stockable-kit-document using a txnDefinition key instead of an ID, the request fails. Using a txnDefinition key will be supported in an upcoming release.