Skip to content

API reference

Hires from recruiting tools

Candidates hired in Teamtailor or Greenhouse waiting for HR, and the tool's departments for the team mapping. Adding, linking and dismissing happen in the web app.

5 actions · base URL https://api.bizisy.com/v1 · generated from the same definitions as the API.

List hires from recruiting tools#

POST/v1/org/ats.hires.listRead

Candidates hired in Teamtailor or Greenhouse, as Bizisy received them: status review (waiting for HR: accept as a pre-hire, link to someone already in Bizisy, or dismiss, in the app), added, linked or dismissed (decided ones keep no candidate details). match: the team (department mapping), catalog title, open position, someone already here with the same email (conflict) and the work email; problems: why one waits. The candidate's personal email is never shown over an API key or MCP. status (default review) or all; source narrows to one tool. Owners, admins and HR. Part of the More integrations module (included): companies with it switched off get module_disabled (an owner or admin switches it on in Manage → Settings → Modules); this read of stored data keeps working while it is off.

Who can call it
Manage key owner admin hr
Keys and apps
Keys and connected apps see the hires without the candidate's personal email.
MCP tool
org_ats_hires_list on HR Assistant
Method
POST with a JSON body, or GET with the input as query parameters

Input

  • status"review" | "all"

    Default "review".

  • source"teamtailor" | "greenhouse"

Returns

  • hiresobject[]required
    12 fields
    • idstringrequired
    • source"teamtailor" | "greenhouse"required
    • application_idstringrequired
    • status"review" | "added" | "linked" | "dismissed"required
    • candidateobject | nullrequired
      4 fields
      • namestringrequired
      • given_namestringrequired
      • family_namestringrequired
      • personal_emailstring | nullrequired

        The candidate's own address (private): null over an API key or MCP.

    • jobobject | nullrequired
      3 fields
      • titlestring | nullrequired
      • departmentstring | nullrequired
      • referencestring | nullrequired
    • start_datestring | nullrequired
    • matchobject | nullrequired
      5 fields
      • teamobject | nullrequired

        From the department mapping in the tool's settings.

        2 fields
        • idstringrequired
        • namestringrequired
      • titleobject | nullrequired

        The job title catalog entry with exactly this name.

        2 fields
        • idstringrequired
        • namestringrequired
      • positionobject | nullrequired

        The one open position with that title in that team.

        2 fields
        • idstringrequired
        • namestringrequired
      • conflictobject | nullrequired

        Someone already in Bizisy with this email: link or dismiss, never changed.

        4 fields
        • idstringrequired
        • namestringrequired
        • titlestring | nullrequired
        • photo_urlstring | nullrequired
      • work_emailstring | nullrequired

        From the tool, or the company's email pattern in the settings.

    • problems"no_start_date" | "start_past" | "no_team" | "title_new" | "no_work_email" | "email_taken"[]required

      Why it waits for HR: no_start_date, start_past, no_team (department not mapped), title_new (not in the catalog), no_work_email, email_taken.

    • personobject | nullrequired
      4 fields
      • idstringrequired
      • namestringrequired
      • titlestring | nullrequired
      • photo_urlstring | nullrequired
    • received_atstringrequired
    • decided_atstring | nullrequired
  • countsobjectrequired
    4 fields
    • reviewintegerrequired
    • addedintegerrequired
    • linkedintegerrequired
    • dismissedintegerrequired

Errors

validation_failed unauthenticated forbidden not_found rate_limited internal

curl
curl https://api.bizisy.com/v1/org/ats.hires.list \
  -H "Authorization: Bearer $BIZISY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status":"all","source":"teamtailor"}'
Response
{
  "data": {
    "hires": [
      {
        "id": "teamtailor:81234",
        "source": "teamtailor",
        "application_id": "81234",
        "status": "review",
        "candidate": {
          "name": "Inês Martins",
          "given_name": "Inês",
          "family_name": "Martins",
          "personal_email": "ines.martins@home.test"
        },
        "job": {
          "title": "Platform Engineer",
          "department": "Product Development",
          "reference": "j9"
        },
        "start_date": "2026-11-02",
        "match": {
          "team": {
            "id": "u2",
            "name": "Platform"
          },
          "title": {
            "id": "t1",
            "name": "Platform Engineer"
          },
          "position": null,
          "conflict": null,
          "work_email": "ines.martins@acme.test"
        },
        "problems": [],
        "person": null,
        "received_at": "2026-10-04T09:00:00.000Z",
        "decided_at": null
      }
    ],
    "counts": {
      "review": 1,
      "added": 3,
      "linked": 0,
      "dismissed": 1
    }
  }
}

Add a hire from a recruiting tool#

POST/v1/org/ats.hires.acceptWrite

Adds a hired candidate (org_ats_hires_list, status review) as a person with their first job, exactly as org_people_hire does: a future start_date makes them a pre-hire, the onboarding checklists that start by themselves start, the team lead becomes the manager when none is given, a position_id fills that position. Send what HR checked: work_email, start_date, title or title_id, unit_id (null for none); given_name, family_name, manager_id and position_id are optional. The candidate's personal email is kept on the person (private). Refused while someone in Bizisy already has that email (link instead). Afterwards the hire keeps no candidate details. Owners, admins and HR, in the app only. Part of the More integrations module (included): companies with it switched off get module_disabled (an owner or admin switches it on in Manage → Settings → Modules).

Web app only
Refused for API keys and connected apps. HR adds a hire from a recruiting tool in the app.
MCP tool
org_ats_hires_accept on HR Assistant
Preview
?dry_run=true runs every check and saves nothing
Retries
An Idempotency-Key prevents a second run, but the result is never stored (it holds a secret or personal data): a retry gets a 409 that points to Activity

Input

  • idstringrequired

    3–200 characters. Pattern ^(teamtailor|greenhouse):.

  • given_namestring

    1–100 characters.

  • family_namestring

    1–100 characters.

  • work_emailemailrequired

    Up to 254 characters.

  • start_datestringrequired

    Pattern ^\d{4}-\d{2}-\d{2}$.

  • titlestring

    1–120 characters.

  • title_idstring
  • unit_idstring | nullrequired
  • manager_idstring | null
  • position_idstring | null

Returns

  • idstringrequired
  • person_idstringrequired
  • onboardingobjectrequired
    2 fields
    • checklistsintegerrequired
    • tasksintegerrequired

Errors

validation_failed unauthenticated forbidden not_found conflict rate_limited internal

curl
curl https://api.bizisy.com/v1/org/ats.hires.accept \
  -H "Authorization: Bearer $BIZISY_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "id": "greenhouse:501",
  "given_name": "Rui",
  "family_name": "Lopes",
  "work_email": "rui.lopes@acme.test",
  "start_date": "2026-11-16",
  "title": "Platform Engineer",
  "unit_id": null,
  "manager_id": "p2",
  "position_id": "pos1"
}'
Response
{
  "data": {
    "id": "greenhouse:501",
    "person_id": "p9",
    "onboarding": {
      "checklists": 1,
      "tasks": 6
    }
  }
}

POST/v1/org/ats.hires.linkWrite

Marks a hired candidate (status review) as someone already in Bizisy (a rehire, an internal move, a duplicate): nothing about that person changes, the hire keeps no candidate details and never comes back. Owners, admins and HR, in the app only. Part of the More integrations module (included): companies with it switched off get module_disabled (an owner or admin switches it on in Manage → Settings → Modules).

Web app only
Refused for API keys and connected apps. Linking a hire to someone already in Bizisy happens in the app.
MCP tool
org_ats_hires_link on HR Assistant
Preview
?dry_run=true runs every check and saves nothing
Retries
An Idempotency-Key replays the first result

Input

  • idstringrequired

    3–200 characters. Pattern ^(teamtailor|greenhouse):.

  • person_idstringrequired

Returns

  • idstringrequired
  • person_idstringrequired

Errors

validation_failed unauthenticated forbidden not_found conflict rate_limited internal

Response
{
  "data": {
    "id": "teamtailor:81234",
    "person_id": "p1"
  }
}

Dismiss a hire from a recruiting tool#

POST/v1/org/ats.hires.dismissWrite

Dismisses a hired candidate (status review) Bizisy should not add: their details are deleted from Bizisy, and the same application never comes back. Owners, admins and HR, in the app only. Part of the More integrations module (included): companies with it switched off get module_disabled (an owner or admin switches it on in Manage → Settings → Modules).

Web app only
Refused for API keys and connected apps. Dismissing a hire happens in the app.
MCP tool
org_ats_hires_dismiss on HR Assistant
Preview
?dry_run=true runs every check and saves nothing
Retries
An Idempotency-Key replays the first result

Input

  • idstringrequired

    3–200 characters. Pattern ^(teamtailor|greenhouse):.

Returns

  • idstringrequired
  • dismissedtruerequired

Errors

validation_failed unauthenticated forbidden not_found conflict rate_limited internal

curl
curl https://api.bizisy.com/v1/org/ats.hires.dismiss \
  -H "Authorization: Bearer $BIZISY_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"id":"teamtailor:81234"}'
Response
{
  "data": {
    "id": "teamtailor:81234",
    "dismissed": true
  }
}

List a recruiting tool's departments#

POST/v1/org/ats.departmentsRead

The departments of a connected Teamtailor or Greenhouse account (id, name), for mapping each to a Bizisy team in the tool's settings. Owners and admins. Part of the More integrations module (included): companies with it switched off get module_disabled (an owner or admin switches it on in Manage → Settings → Modules).

Who can call it
Manage key owner admin
MCP tool
org_ats_departments on HR Assistant
Method
POST with a JSON body, or GET with the input as query parameters

Input

  • source"teamtailor" | "greenhouse"required

Returns

  • departmentsobject[]required
    2 fields
    • idstringrequired
    • namestringrequired

Errors

validation_failed unauthenticated forbidden not_found rate_limited internal

curl
curl https://api.bizisy.com/v1/org/ats.departments \
  -H "Authorization: Bearer $BIZISY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"source":"teamtailor"}'
Response
{
  "data": {
    "departments": [
      {
        "id": "d1",
        "name": "Product Development"
      }
    ]
  }
}

Something missing or wrong on this page? Write to hello@bizisy.com.

Developer docs