Execute a batch of independent subrequests using the Salesforce REST /composite/batch resource
domain: developer.salesforce.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Salesforce Bulk API 2.0 limits — the full failure-mode walkthrough related to developer.salesforce.com, checked against official docs, with linked verified routes.
Steps
Send POST to /services/data/v<version>/composite/batch with a batchRequests array, each specifying a method, url, and optional richInput body.
This resource executes up to 25 subrequests in a single call, each counting individually against API rate limits.
The response bundles each subrequest's HTTP status and body in one response body, in the same order as submitted.
Subrequests execute serially but independently — later subrequests cannot reference or use data returned from earlier ones in the same batch.
Plan around the 10-minute batch timeout; if the whole batch doesn't complete within that window it times out.
Known gotchas
Unlike the Composite (non-batch) resource, /composite/batch has no allOrNone rollback — a failed subrequest does not undo commits already made by earlier subrequests in the same batch.
Because subrequests can't reference each other's results, use the plain Composite resource instead if you need to chain a create's output ID into a later subrequest.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?