Fetch an X-CSRF-Token via a preflight GET as described in the token-fetch route
Construct a multipart/mixed request body: each change set uses Content-Type: multipart/mixed with its own boundary, and each individual operation is a Content-Type: application/http part
POST the batch to the endpoint <ServiceRoot>/$batch with headers Content-Type: multipart/mixed; boundary=<outer-boundary> and X-CSRF-Token: <token>
Parse the multipart response: each part carries its own HTTP status line; a 200 on the outer response does not mean all inner operations succeeded
Rollback semantics: within a change set, any single operation failure causes the entire change set to roll back; operations outside change sets are independent
Known gotchas
Queries (GET) cannot be placed inside a change set — they must appear as individual parts outside any change set boundary
SAP Gateway enforces a limit on the number of operations per batch request; consult your system's configuration, as the default cap can be low for large imports
Boundary strings must be unique and must not appear inside the request body; use a UUID-derived boundary to avoid collisions
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp