Use POST /crm/v4/associations/{fromObjectType}/{toObjectType}/batch/create to associate multiple record pairs in a single API call
Build the request body as an inputs array where each element contains fromObjectId, toObjectId, and an array of associationTypes each with typeId and, optionally, category
Limit each batch to the documented maximum inputs per request; consult current docs for the current batch size limit
Process the response's errors array; a partial-failure response still returns a 207 status with successfully created associations and a list of failed ones
Retry failed inputs individually or in a smaller batch after resolving the error (e.g., object not found, duplicate association)
Use batch/read and batch/archive endpoints analogously for bulk reads and deletes
Known gotchas
A 207 Multi-Status response means some associations succeeded and some failed; do not treat a non-4xx status as full success
Associating a record pair that already has the same typeId does not create a duplicate but also does not error; the operation is idempotent for that type
Rate limits apply per-endpoint; batch calls count as one API call against the rate limit regardless of how many record pairs they contain
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