REST Record Service: Async Bulk Endpoint Goes GA
The async bulk endpoint for the REST Record Service exits beta. Integration platforms can now POST batched record operations and poll a job status URL instead of holding HTTP connections open.
One of the long-standing gaps in REST Record Service was that every create/update was synchronous and serial — fine for a UI, terrible for data loads. 2026.1 promotes the async bulk endpoint to GA.
How it works
You POST a batch envelope of operations against /services/rest/record/v1/async/bulk. The response is a 202 Accepted with a jobId and a status URL you poll until the job reaches a terminal state. Successful and failed records are returned per-row so partial-success batches no longer require manual reconciliation.
Integration platform impact
- Boomi / Celigo / Workato: connectors that currently iterate one record at a time can be re-templated to batch — expect 5-20x throughput on customer/contact upserts.
- OAuth 2.0 only: the async endpoint does not accept TBA. If you are still on token-based auth for REST, this is your forcing function.
- Concurrency limits: jobs count against the account-level concurrency cap, not the per-user cap — coordinate with whoever owns your other integrations before flipping volume.
What to do
Audit any integration that uses synchronous POST /record/v1/<type> in a loop. Those are the first candidates for migration. Save your existing flow as a fallback — the async path returns errors differently and your downstream error handlers will need updating.
Source: Oracle NetSuite Release Notes