Skip to main content
Spott offers an extensive REST API to build integrations on top of your data. It exposes most of Spott’s records and actions: candidates, jobs, companies, contacts, applications, placements, notes, tasks, and more. The full endpoint reference, with request and response shapes, an interactive “Try it” playground, and pagination behavior, is in the sidebar of this tab, grouped by record type (Candidates, Jobs, Applications, and more).

​
Common use cases

  • Build a custom dashboard on your Spott data.
  • Push data from external systems into Spott, for example custom intake forms or an HRIS sync.
  • Pull data out of Spott for BI tools and data warehouses.
  • Trigger downstream workflows when something happens in Spott, combined with webhooks.

​
Authentication

  • The base URL is https://api.gospott.com.
  • Private endpoints require an x-api-key header with your API key.
  • Public endpoints (for example, job board content) need no key; they are scoped by the publicTenantSlug path parameter instead.

​
API keys

Generate keys under Settings → API, where you also find links to this API documentation and the MCP setup (admin permissions required):
The API settings page with documentation links and API keys
  • Copy the key immediately. It is shown only once; if you lose it, generate a new one.
  • Each key is bound to both the workspace and the user who created it. Every action performed with the key is attributed to that user; there is no way to pass a different actor in the request. This protects audit trails and prevents impersonation.
  • If your integration acts on behalf of multiple users, each user needs their own API key.

​
Rate limits and pagination

  • Endpoints are rate limited at 600 requests per minute. Exceeding the limit returns 429 Too Many Requests.
  • List endpoints use cursor-based pagination: pass the cursor value from the previous response to fetch the next page.

​
Three ways to build on Spott

  • REST API: traditional integrations, scripts, and data sync at scale.
  • Webhooks: Spott pushes events to your endpoint.
  • MCP: AI assistants interact with Spott conversationally.
They are complementary: webhooks tell you something happened, the API lets you fetch and change the details, and MCP puts an AI assistant in the loop.