Loxo Open API: create and manage webhooks for record changes
domain: loxo.co · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm you have a Bearer API key with Open API access as described in Loxo's authentication docs.
POST to https://{domain}/api/{agency_slug}/webhooks with item_type (e.g. candidate, job, placement, person, company, deal), action (create, update, or destroy), and endpoint_url in the request body.
List existing webhooks with GET https://{domain}/api/{agency_slug}/webhooks to audit what's currently configured.
Fetch, update, or delete a specific webhook via GET/PUT/DELETE https://{domain}/api/{agency_slug}/webhooks/{id}.
Implement your endpoint to handle each item_type/action combination you subscribed to, since Loxo webhooks replace polling for change detection.
Known gotchas
item_type is restricted to a fixed enum (candidate, company, deal, job, person, person_education_profile, person_event, person_job_profile, placement, placement_split) — arbitrary custom object types aren't supported.
action is limited to create, update, and destroy — there's no separate event for field-level changes, so you must diff payloads yourself if you need granular change detection.
Webhooks are the recommended alternative to polling specifically to avoid rate/403 issues from frequent GET requests — don't run both a tight polling loop and webhooks for the same data.
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?