Identify your Braze REST endpoint (e.g., https://rest.iad-01.braze.com) — this is cluster-specific and found in the Braze dashboard under Settings > APIs and Identifiers.
Track user attributes by POSTing to {endpoint}/users/track with Authorization: Bearer {API_KEY} and a JSON body containing an attributes array, each item with an external_id and the custom or standard attributes to set.
Log custom events in the same call or separately by including an events array in the /users/track payload, each item with external_id, name (event name), and time (ISO 8601).
To trigger an API-triggered campaign, first create the campaign in the Braze dashboard with delivery type 'API-triggered', then send it via POST {endpoint}/campaigns/trigger/send with campaign_id and a recipients array.
For transactional or Canvas flows, use {endpoint}/canvas/trigger/send similarly with a canvas_id to trigger a specific Canvas entry.
Known gotchas
The REST endpoint URL is cluster-specific; using the wrong cluster URL (e.g., iad-01 vs iad-06) returns connection errors or 404s that are easy to misdiagnose as auth failures.
The /users/track endpoint accepts up to 75 events, 75 attribute updates, and 75 purchases per request; exceeding these limits causes the entire request to be rejected, not partially processed.
API-triggered campaigns must be set to API-triggered delivery in the dashboard before the trigger/send call will work; campaigns configured for scheduled or action-based delivery cannot be triggered via the API.
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