Build on FastHire.

The FastHire API is organized around the same objects recruiters work with in the app: searches (an AI sourcing run against a role), the candidates it surfaces, lists recruiters curate from results, sequences that run outreach across LinkedIn, email and in-app steps, the inbox those sequences populate, and interviews scheduled from a reply. Every object is scoped to one organization — your API key determines which org’s data you see.

The API accepts and returns application/json, uses standard HTTP response codes, and is versioned in the URL.

https://api.thefasthire.com/v1

Authenticate by sending a secret API key as a bearer token. Generate keys from Settings → Developer in the FastHire app — each key is scoped to one org and inherits no more access than the role that created it (an ORG_ADMIN key can manage sequences and connections; a RECRUITER key cannot).

curl https://api.thefasthire.com/v1/searches \
  -H "Authorization: Bearer fh_live_51H8x...cQ2k"

Errors return a 4xx/5xx status and a JSON body describing what went wrong.

{
  "error": {
    "type": "invalid_request",
    "code": "missing_field",
    "message": "criteria.mandatory is required for sourceType=MANUAL",
    "field": "criteria.mandatory"
  }
}

List endpoints are cursor-paginated. Pass limit (default 25, max 100) and cursor from the previous page’s next_cursor.

{
  "data": [ /* … */ ],
  "has_more": true,
  "next_cursor": "eyJpZCI6ImNuZF85..."
}

Every response carries rate-limit headers; the default org limit is 300 requests/minute, shared across all keys on that org.

A search is one AI sourcing run for a role — a natural-language brief, a pasted job description, or a manually-built candidate set. Activating one spins up an agent that scores candidates against mandatory and desirable criteria.

{
  "data": [
    {
      "id": "src_7bWmA1...",
      "name": "Senior Backend Engineer — Sydney",
      "source_type": "JOB_DESCRIPTION",
      "status": "COMPLETE",
      "result_count": 143,
      "owner_id": "usr_2kTQm...",
      "created_at": "2026-08-12T04:11:00Z"
    }
  ],
  "has_more": false,
  "next_cursor": null
}

curl https://api.thefasthire.com/v1/searches \
  -X POST -H "Authorization: Bearer $FASTHIRE_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Senior Backend Engineer — Sydney",
    "source_type": "JOB_DESCRIPTION",
    "criteria": {
      "mandatory": ["5+ years backend", "Right to work in Australia"],
      "desirable": ["Distributed systems", "Fintech background"]
    }
  }'

{
  "data": [
    {
      "candidate_id": "cnd_9mK2pQ...",
      "name": "Priya Nair",
      "headline": "Staff Engineer at Canva",
      "match_score": 0.94,
      "match_tier": "TOP_MATCH",
      "match_reasoning": "7 yrs backend, distributed systems at scale, AU-based."
    }
  ],
  "has_more": true,
  "next_cursor": "eyJpZCI6InNy..."
}

A candidate record is deduplicated per org by source profile, and accumulates results, list memberships, sequence history, and interviews as it moves through your pipeline.

{
  "id": "cnd_9mK2pQ...",
  "name": "Priya Nair",
  "headline": "Staff Engineer at Canva",
  "email": "priya.nair@example.com",
  "phone": null,
  "linkedin_url": "https://linkedin.com/in/priyanair",
  "location": "Sydney, Australia",
  "education": [ { "school": "UNSW", "degree": "BSc Computer Science" } ],
  "experience": [ { "company": "Canva", "title": "Staff Engineer", "years": 3 } ],
  "skills": ["Go", "Kubernetes", "PostgreSQL"],
  "first_seen_at": "2026-08-12T04:12:31Z"
}

Lists are recruiter-curated candidate sets, independent of any one search — the unit sequences target for outreach.

A sequence is an outreach campaign: an ordered set of LinkedIn, email, and in-app steps run against one or more target lists.

curl https://api.thefasthire.com/v1/sequences/seq_4LpN.../ \
  -X PATCH -H "Authorization: Bearer $FASTHIRE_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "status": "ACTIVE" }'

Every send and reply across LinkedIn, email, and WhatsApp lands in one per-candidate thread.

{
  "data": [
    {
      "id": "msg_1QvD...",
      "channel": "EMAIL",
      "direction": "INBOUND",
      "body": "Thanks for reaching out — happy to chat this week.",
      "status": "REPLIED",
      "sent_at": "2026-08-19T02:04:00Z",
      "read_at": null
    }
  ]
}

Interviews link a candidate, a recruiter, and a time — optionally backed by a real Calendar connection.

Subscribe to an endpoint from Settings → Developer → Webhooks to be notified as events happen, instead of polling.

{
  "id": "evt_8pXeC...",
  "type": "candidate.replied",
  "created_at": "2026-08-19T02:04:00Z",
  "data": { /* the object, shaped like its REST response */ }
}

Each request carries an X-FastHire-Signature header — an HMAC-SHA256 of the raw body using your endpoint’s signing secret. Verify it before trusting the payload, and return a 2xx within 10 seconds or FastHire retries with backoff for up to 24 hours.

This document is the working spec for FastHire’s public API, generated from the live recruiter data model as of August 2026. Object and field names here are intended to match the eventual implementation exactly, so this page can move from spec to shipped documentation with no renaming pass.

Not yet scoped: candidate CSV import via API (currently UI-only), managing team members/invitations, and org-level billing endpoints. Flag priorities to the FastHire team before the v1 build starts.