Generate a Hightouch API key from your Hightouch workspace settings.
Identify the numeric sync ID you want to trigger from the Hightouch UI or via the syncs list endpoint.
POST to https://api.hightouch.com/api/v1/syncs/YOUR_SYNC_ID/trigger with Authorization: Bearer YOUR_API_KEY and Content-Type application/json.
Optionally include a JSON body with fullResync set to true if you want to re-sync all records rather than only changed records.
Capture the id field from the response to identify the sync request.
Poll GET /api/v1/syncs/YOUR_SYNC_ID to check the status field until it reflects a completed or failed state.
Known gotchas
The fullResync option causes all records to be processed regardless of change tracking and can significantly increase runtime and destination API usage — use it sparingly.
API keys in Hightouch are workspace-scoped; a key from one workspace cannot be used to trigger syncs in another workspace.
If a sync is already running, triggering another run may be queued or rejected — check the current sync status before triggering to avoid unintended concurrent runs.
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