Teamtailor

Teamtailor (via Apideck)

Access Teamtailor through Apideck's ATS unified API — one of 11 ATS connectors that share the same method surface. Code you write here ports to Greenhouse, Workday, Lever and 7 other ATS connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Teamtailor plumbing.

Beta connector. Teamtailor is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.

Quick facts

• Apideck serviceId: teamtailor
• Unified API: ATS
• Auth type: apiKey
• Status: beta
• Apideck setup guide: Connection guide
• Gotchas: page
• Teamtailor docs: https://docs.teamtailor.com
• Homepage: https://www.teamtailor.com/

When to use this skill

Activate this skill when the user explicitly wants to work with Teamtailor — for example, "list open jobs in Teamtailor" or "move an applicant through stages in Teamtailor". This skill teaches the agent:

1. Which Apideck unified API covers Teamtailor (ATS)
2. The correct serviceId to pass on every call (teamtailor)
3. Teamtailor-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

• apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-rest

For the raw OpenAPI spec:

• ATS: https://specs.apideck.com/ats.yml · API Explorer

Minimal example (TypeScript)

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List applicants in Teamtailor
const { data } = await apideck.ats.applicants.list({
  serviceId: "teamtailor",
});

Portable across 11 ATS connectors

The Apideck ATS unified API exposes the same methods for every connector in its catalog. Switching from Teamtailor to another ATS connector is a one-string change — no rewrite, no new SDK.

// Today — Teamtailor
await apideck.ats.applicants.list({ serviceId: "teamtailor" });

// Tomorrow — same code, different connector
await apideck.ats.applicants.list({ serviceId: "greenhouse" });
await apideck.ats.applicants.list({ serviceId: "workday" });

This is the compounding advantage of using Apideck over integrating Teamtailor directly: code against the unified ATS API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.

Authentication

• Type: API Key
• Managed by: Apideck Vault — the user pastes their Teamtailor API key into the Vault modal; Apideck stores it encrypted and injects it on every request.
• Rotation: if the user rotates their key, they re-enter it in Vault. No code changes needed.

Setup guide: Apideck publishes a step-by-step guide for registering an OAuth app / configuring credentials for Teamtailor — see https://developers.apideck.com/connectors/teamtailor/docs/consumer+connection. Use that as the authoritative source when walking users through connection setup.

See apideck-best-practices for Vault setup, connection lifecycle, and handling re-auth flows.

Verifying coverage

Not every ATS operation is supported by every connector. Always verify before assuming a method works:

curl 'https://unify.apideck.com/connector/connectors/teamtailor' \
  -H "Authorization: Bearer ${APIDECK_API_KEY}" \
  -H "x-apideck-app-id: ${APIDECK_APP_ID}"

See apideck-connector-coverage for patterns around UnsupportedOperationError and connector-specific fallbacks.

Escape hatch: Proxy API

When an endpoint isn't covered by the ATS unified API, use Apideck's Proxy to call Teamtailor directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Teamtailor's own API:

curl 'https://unify.apideck.com/proxy' \
  -H "Authorization: Bearer ${APIDECK_API_KEY}" \
  -H "x-apideck-app-id: ${APIDECK_APP_ID}" \
  -H "x-apideck-consumer-id: ${CONSUMER_ID}" \
  -H "x-apideck-service-id: teamtailor" \
  -H "x-apideck-downstream-url: <target endpoint on Teamtailor>" \
  -H "x-apideck-downstream-method: GET"

See Teamtailor's API docs for available endpoints.

Sibling connectors

Other ATS connectors that share this unified API surface (same method signatures, just change serviceId):

greenhouse, workday, lever, workable (beta), bullhorn-ats (beta), freshteam, jobadder (beta), recruitee, and 2 more.

See also

• Apideck connection guide for Teamtailor
• ATS OpenAPI spec · API Explorer
• apideck-connector-coverage — programmatic coverage checks
• apideck-best-practices — architecture, Vault, pagination, error handling
• apideck-node — TypeScript / Node SDK patterns
• Teamtailor official docs