Spott

Use Spott as an ATS/CRM write target: push sourced + enriched candidates and leads, sync clients (companies-as-accounts) and their contacts, and move applications through a job's pipeline. Spott also exposes notes, tasks, placements, opportunities, and a tenant-wide people search.

Capabilities

Guidance

• Auth is an x-api-key header, generated in Spott under Settings → API (admin permissions required; the key is shown once). Each key is bound to both the workspace and the user who created it, and every action is attributed to that user — an integration acting for multiple users needs a key per user.
• Production ATS writes — dry-run one record, show payload + response, confirm before bulk.
• Creating a job needs a pipeline stageId, and creating an application needs stageId + statusId — resolve them first with get_vacancy_stages, get_client_stages, or get_opportunity_stages before writing.
• Record deletion is not exposed for any resource.
• List name resolution is exact-but-case-insensitive; an ambiguous name (more than one list sharing it) fails rather than guessing which list was meant.
• Linking or unlinking records to a list is capped at 250 ids per call — an over-limit or duplicate id list is rejected, not trimmed.
• add_to_list_by_name won't create a missing list, and removing records from a list does not delete the records.
• Handoff: sourced + enriched candidates/leads → create_candidate → create_application → review in Spott.

hyreflow tools execute spott create_candidate \
  --payload '{"firstName":"Ada","lastName":"Lovelace","email":"[email protected]"}'

hyreflow tools execute spott add_to_list_by_name \
  --payload '{"list_name":"Acme Q4 shortlist","record_ids":["candidate-123","candidate-456"]}'

Rate limits & bulk writes

Spott publishes a rate limit of 600 requests/minute per API key — the adapter paces to that number rather than guessing a conservative default. Most list endpoints use cursor pagination; placements use offset pagination instead. Use create_candidates_batch, create_clients_batch, and create_notes_batch for large single-record pushes, or the native bulk endpoints for applications — batch helpers pace automatically. See Bulk pushes to ATS / recruiting CRM.