Bulk fetch candidates - Taptalent Partner API

curl --request POST \
  --url https://partner-api.taptalent.io/v1/partner/candidates/bulk-fetch \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "candidateIds": [
    12345,
    12346,
    12347
  ]
}
'

{
  "status": "success",
  "data": [
    {
      "id": 12345,
      "firstName": "John",
      "lastName": "Doe",
      "email": "john.doe@example.com",
      "phone": "+1234567890",
      "currentJobTitle": "Software Engineer",
      "currentCompany": "Tech Corp",
      "city": "San Francisco",
      "country": "United States",
      "skills": [
        "JavaScript",
        "React",
        "Node.js"
      ],
      "resume": "https://storage.example.com/resumes/john-doe.pdf",
      "majors": [
        "Computer Science"
      ],
      "summary": "Experienced software engineer...",
      "languages": [
        "English"
      ],
      "educations": [
        {
          "degree": "Bachelor's",
          "field": "Computer Science",
          "institution": "University"
        }
      ],
      "workExperiences": [
        {
          "title": "Software Engineer",
          "company": "Tech Corp",
          "duration": "2 years"
        }
      ],
      "projectExperiences": [],
      "certifications": [],
      "githubUrl": "https://github.com/johndoe",
      "linkedin": "https://linkedin.com/in/johndoe"
    }
  ],
  "invalidCandidateIds": [
    12347
  ]
}

POST

/

candidates

/

bulk-fetch

curl --request POST \
  --url https://partner-api.taptalent.io/v1/partner/candidates/bulk-fetch \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "candidateIds": [
    12345,
    12346,
    12347
  ]
}
'

{
  "status": "success",
  "data": [
    {
      "id": 12345,
      "firstName": "John",
      "lastName": "Doe",
      "email": "john.doe@example.com",
      "phone": "+1234567890",
      "currentJobTitle": "Software Engineer",
      "currentCompany": "Tech Corp",
      "city": "San Francisco",
      "country": "United States",
      "skills": [
        "JavaScript",
        "React",
        "Node.js"
      ],
      "resume": "https://storage.example.com/resumes/john-doe.pdf",
      "majors": [
        "Computer Science"
      ],
      "summary": "Experienced software engineer...",
      "languages": [
        "English"
      ],
      "educations": [
        {
          "degree": "Bachelor's",
          "field": "Computer Science",
          "institution": "University"
        }
      ],
      "workExperiences": [
        {
          "title": "Software Engineer",
          "company": "Tech Corp",
          "duration": "2 years"
        }
      ],
      "projectExperiences": [],
      "certifications": [],
      "githubUrl": "https://github.com/johndoe",
      "linkedin": "https://linkedin.com/in/johndoe"
    }
  ],
  "invalidCandidateIds": [
    12347
  ]
}

Authorizations

Authorization

string

header

required

Company-scoped API key. Production keys are prefixed sk_live_, sandbox keys sk_test_, each followed by 22 base62 characters (pattern ^sk_(live|test)_[0-9A-Za-z]{22}$). Generate keys in the TapTalent dashboard under Account Settings → Developers → API Key Management; a key is shown once at generation and old keys are invalidated immediately on regeneration.

Body

application/json

Request body for the bulk-fetch candidates endpoint.

candidateIds

(integer | string)[]

required

Array of candidate IDs to fetch. Maximum 100 IDs per request. Each candidate ID must be a valid non-empty string or number.

Required array length: 1 - 100 elements

Response

Candidates matching the requested IDs. IDs that were not found are listed in invalidCandidateIds (present only when some IDs are invalid).

Success envelope for the bulk-fetch candidates endpoint.

status

enum<string>

required

Response status ("success").

Available options:

success

data

object[]

required

Array of candidate objects.

Show child attributes

invalidCandidateIds

(integer | string)[]

Candidate IDs that were not found. Only included in the response when at least one requested ID is invalid. IDs are echoed as submitted (integer or string); the documented example shows integers.