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_liston HR Assistant- Method
POSTwith a JSON body, orGETwith the input as query parameters
Input
status"review" | "all"Default
"review".source"teamtailor" | "greenhouse"
Returns
hiresobject[]required12 fields
idstringrequiredsource"teamtailor" | "greenhouse"requiredapplication_idstringrequiredstatus"review" | "added" | "linked" | "dismissed"requiredcandidateobject | nullrequired4 fields
namestringrequiredgiven_namestringrequiredfamily_namestringrequiredpersonal_emailstring | nullrequiredThe candidate's own address (private): null over an API key or MCP.
jobobject | nullrequired3 fields
titlestring | nullrequireddepartmentstring | nullrequiredreferencestring | nullrequired
start_datestring | nullrequiredmatchobject | nullrequired5 fields
teamobject | nullrequiredFrom the department mapping in the tool's settings.
2 fields
idstringrequirednamestringrequired
titleobject | nullrequiredThe job title catalog entry with exactly this name.
2 fields
idstringrequirednamestringrequired
positionobject | nullrequiredThe one open position with that title in that team.
2 fields
idstringrequirednamestringrequired
conflictobject | nullrequiredSomeone already in Bizisy with this email: link or dismiss, never changed.
4 fields
idstringrequirednamestringrequiredtitlestring | nullrequiredphoto_urlstring | nullrequired
work_emailstring | nullrequiredFrom 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"[]requiredWhy 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 | nullrequired4 fields
idstringrequirednamestringrequiredtitlestring | nullrequiredphoto_urlstring | nullrequired
received_atstringrequireddecided_atstring | nullrequired
countsobjectrequired4 fields
reviewintegerrequiredaddedintegerrequiredlinkedintegerrequireddismissedintegerrequired
Errors
validation_failed unauthenticated forbidden not_found rate_limited internal
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"}'const res = await fetch('https://api.bizisy.com/v1/org/ats.hires.list', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.BIZISY_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
"status": "all",
"source": "teamtailor"
}),
});
const body = await res.json();
if (!res.ok) throw new Error(`${body.error.code}: ${body.error.message}`);
console.log(body.data);import os
import requests
res = requests.post(
"https://api.bizisy.com/v1/org/ats.hires.list",
headers={"Authorization": f"Bearer {os.environ['BIZISY_API_KEY']}"},
json={
"status": "all",
"source": "teamtailor",
},
)
body = res.json()
if not res.ok:
raise RuntimeError(f"{body['error']['code']}: {body['error']['message']}")
print(body["data"]){
"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_accepton HR Assistant- Preview
?dry_run=trueruns 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
idstringrequired3–200 characters. Pattern
^(teamtailor|greenhouse):.given_namestring1–100 characters.
family_namestring1–100 characters.
work_emailemailrequiredUp to 254 characters.
start_datestringrequiredPattern
^\d{4}-\d{2}-\d{2}$.titlestring1–120 characters.
title_idstringunit_idstring | nullrequiredmanager_idstring | nullposition_idstring | null
Returns
idstringrequiredperson_idstringrequiredonboardingobjectrequired2 fields
checklistsintegerrequiredtasksintegerrequired
Errors
validation_failed unauthenticated forbidden not_found conflict rate_limited internal
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"
}'const res = await fetch('https://api.bizisy.com/v1/org/ats.hires.accept', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.BIZISY_API_KEY}`,
'Content-Type': 'application/json',
'Idempotency-Key': crypto.randomUUID(),
},
body: JSON.stringify({
"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"
}),
});
const body = await res.json();
if (!res.ok) throw new Error(`${body.error.code}: ${body.error.message}`);
console.log(body.data);import os, uuid
import requests
res = requests.post(
"https://api.bizisy.com/v1/org/ats.hires.accept",
headers={"Authorization": f"Bearer {os.environ['BIZISY_API_KEY']}", "Idempotency-Key": str(uuid.uuid4())},
json={
"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": None,
"manager_id": "p2",
"position_id": "pos1",
},
)
body = res.json()
if not res.ok:
raise RuntimeError(f"{body['error']['code']}: {body['error']['message']}")
print(body["data"]){
"data": {
"id": "greenhouse:501",
"person_id": "p9",
"onboarding": {
"checklists": 1,
"tasks": 6
}
}
}Link a hire to someone already in Bizisy#
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_linkon HR Assistant- Preview
?dry_run=trueruns every check and saves nothing- Retries
- An Idempotency-Key replays the first result
Input
idstringrequired3–200 characters. Pattern
^(teamtailor|greenhouse):.person_idstringrequired
Returns
idstringrequiredperson_idstringrequired
Errors
validation_failed unauthenticated forbidden not_found conflict rate_limited internal
curl https://api.bizisy.com/v1/org/ats.hires.link \
-H "Authorization: Bearer $BIZISY_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"id":"teamtailor:81234","person_id":"p1"}'const res = await fetch('https://api.bizisy.com/v1/org/ats.hires.link', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.BIZISY_API_KEY}`,
'Content-Type': 'application/json',
'Idempotency-Key': crypto.randomUUID(),
},
body: JSON.stringify({
"id": "teamtailor:81234",
"person_id": "p1"
}),
});
const body = await res.json();
if (!res.ok) throw new Error(`${body.error.code}: ${body.error.message}`);
console.log(body.data);import os, uuid
import requests
res = requests.post(
"https://api.bizisy.com/v1/org/ats.hires.link",
headers={"Authorization": f"Bearer {os.environ['BIZISY_API_KEY']}", "Idempotency-Key": str(uuid.uuid4())},
json={
"id": "teamtailor:81234",
"person_id": "p1",
},
)
body = res.json()
if not res.ok:
raise RuntimeError(f"{body['error']['code']}: {body['error']['message']}")
print(body["data"]){
"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_dismisson HR Assistant- Preview
?dry_run=trueruns every check and saves nothing- Retries
- An Idempotency-Key replays the first result
Input
idstringrequired3–200 characters. Pattern
^(teamtailor|greenhouse):.
Returns
idstringrequireddismissedtruerequired
Errors
validation_failed unauthenticated forbidden not_found conflict rate_limited internal
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"}'const res = await fetch('https://api.bizisy.com/v1/org/ats.hires.dismiss', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.BIZISY_API_KEY}`,
'Content-Type': 'application/json',
'Idempotency-Key': crypto.randomUUID(),
},
body: JSON.stringify({
"id": "teamtailor:81234"
}),
});
const body = await res.json();
if (!res.ok) throw new Error(`${body.error.code}: ${body.error.message}`);
console.log(body.data);import os, uuid
import requests
res = requests.post(
"https://api.bizisy.com/v1/org/ats.hires.dismiss",
headers={"Authorization": f"Bearer {os.environ['BIZISY_API_KEY']}", "Idempotency-Key": str(uuid.uuid4())},
json={
"id": "teamtailor:81234",
},
)
body = res.json()
if not res.ok:
raise RuntimeError(f"{body['error']['code']}: {body['error']['message']}")
print(body["data"]){
"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_departmentson HR Assistant- Method
POSTwith a JSON body, orGETwith the input as query parameters
Input
source"teamtailor" | "greenhouse"required
Returns
departmentsobject[]required2 fields
idstringrequirednamestringrequired
Errors
validation_failed unauthenticated forbidden not_found rate_limited internal
curl https://api.bizisy.com/v1/org/ats.departments \
-H "Authorization: Bearer $BIZISY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"source":"teamtailor"}'const res = await fetch('https://api.bizisy.com/v1/org/ats.departments', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.BIZISY_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
"source": "teamtailor"
}),
});
const body = await res.json();
if (!res.ok) throw new Error(`${body.error.code}: ${body.error.message}`);
console.log(body.data);import os
import requests
res = requests.post(
"https://api.bizisy.com/v1/org/ats.departments",
headers={"Authorization": f"Bearer {os.environ['BIZISY_API_KEY']}"},
json={
"source": "teamtailor",
},
)
body = res.json()
if not res.ok:
raise RuntimeError(f"{body['error']['code']}: {body['error']['message']}")
print(body["data"]){
"data": {
"departments": [
{
"id": "d1",
"name": "Product Development"
}
]
}
}Something missing or wrong on this page? Write to hello@bizisy.com.