Migrate from Teamtailor: what moves, API key, limits
What Shuttio reads from Teamtailor, where it lands in Ashby, Lever, Greenhouse, which permissions it needs and why, and what does not move.
Last updated: 20 November 2026
Shuttio connects to Teamtailor with an API key and the region of your account, Europe or North America. A Teamtailor admin makes the key under Settings, Integrations, API keys, with the Admin read scope. Shuttio sends the key only to Teamtailor's own addresses: the region's API host (api.teamtailor.com for Europe, api.na.teamtailor.com for North America) and teamtailor.com upload links. Upload links on other storage hosts are fetched without it.
Object by object: What objects are supported for Teamtailor migrations.
What Shuttio reads and moves
- Jobs: every state, with the department, locations, recruiter and the job's ordered stages. Listing all states needs an Internal or Admin key.
- Users, departments, locations and rejection reasons (Teamtailor's reject reasons).
- Candidates: listed in pages of 30 by id, with their uploads and custom field values loaded in the same request. A Teamtailor candidate has one email and any number of job applications, so one candidate comes with all of its applications. A select field's value is written as the option's text.
- Job applications: each has its stage, rejection (reason and date), source, referring URL and job match score. An application is hired when its stage is of the hired type.
- Movements: Teamtailor's stage moves give the dated stage history. When there are none, the history is the current stage at the date the application entered it.
- Notes: sit under their application and author. A private note stays private, a note with a rating becomes feedback, a note tied to no application goes on the latest one, and a note on a candidate with no application goes into the profile.
- Interviews: arrive as feedback on the application of the interview's job, with the interview's note and each scorecard criterion with its score.
- Job offers: the latest offer of an application, with its status, dates and detail fields. Earlier offers of the same application are not moved.
- Answers: answers to application questions and form answers belong to the candidate, so they go on the latest application, with the question text.
- Uploads: the resume and the uploads. One tied to a job goes on that job's application, and one tied to no job goes on the candidate.
Where each thing lands
| Teamtailor object | In Ashby | In Lever | In Greenhouse |
|---|---|---|---|
| Candidates | Its own object, or the one you already have with that name | Its own object, or the one you already have with that name | Its own object, or the one you already have with that name |
Notes, tasks, meetings, calls, files, owners and lists depend on the destination. This is the row for Teamtailor, generated from the same tables the runner uses:
Into Ashby
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Teamtailor | Candidates | Yes | No | No | No | No | Yes | Yes | No |
Into Lever
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Teamtailor | Candidates | Yes | No | No | No | No | Yes | Yes | No |
Into Greenhouse
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Teamtailor | Candidates | Yes | No | No | No | No | Yes | Yes | No |
In Ashby, Lever and Greenhouse, notes and files move with the candidate; interviews and offers are written as notes, offers as private notes.
Each destination's own article says how its data is written: Ashby, Lever, Greenhouse.
The API key and why
| What | Why Shuttio needs it |
|---|---|
| An API key with the Admin read scope | Teamtailor's scopes are Public, Internal and Admin, each read, write or read and write. Candidates, job applications, notes, interviews, job offers and uploads need Admin. Teamtailor's public API has no OAuth, so a pasted key is the only way to connect. |
| The region | Europe or North America. Shuttio sends its API requests to that region's host, and the key is refused at connect when Teamtailor rejects it for the chosen region. |
| What the connect step checks | Jobs and candidates first: a key that cannot read either is refused. Then notes, interviews, job offers and movements. A key that cannot read one of those still connects, and the run says which part was left out. |
Teamtailor needs an X-Api-Version header on every request. Shuttio sends 20240904.
What Teamtailor's API does not give
- Not read: EEO answers, emails and messages, todos, onboardings and requisition approvals. Teamtailor's API reference has no endpoint to read EEO answers or sent emails.
- No per-candidate filter: the reference documents none for notes, interviews, offers, applications or stage moves, so those lists are read for the whole account, not per candidate.
- Huge lists: the answers and actions lists can answer 500 when fetched whole, so Shuttio never lists them whole. Answers are read per candidate.
- Files: upload links last one minute. Shuttio asks for a fresh link once when one has aged, and a file that is gone is not copied. A file over 30 MB is not copied either.
Known limits
- Rate limit: Teamtailor allows 50 requests every 10 seconds, then answers 429. Shuttio sends one every 220 ms, waits for the reset the response names, and pauses the run after five refusals or a wait over a minute.
- Interviews: Shuttio reads the creation date, note and scorecard scores (no scheduled time) and writes each as feedback. One with no note and no scores is skipped.
- Job offers: only the latest offer of an application moves. Earlier offers of the same application are not moved.
- Time: before the first candidate, Shuttio reads the account-wide lists (applications, stage moves, notes, interviews, scorecard scores, job offers) once, 30 rows a page, and keeps them for 15 minutes under the migration. After that it makes two requests per candidate. A large account takes hours, and the run pauses when Teamtailor asks it to slow down.
Not answered here? Email help@shuttio.com.