Talentino Docs

Getting Started

Mint a Partner API key and make your first call.

The Partner API v1 lets an external platform push work into Talentino without a logged-in user session: import Resumes (single or bulk) and launch Job Matches, then poll the existing read endpoints for results. All write endpoints live under /api/v1 and authenticate with a Business-Unit-scoped API key.

1. Mint an API key

API keys are created from the Talentino app, not the API.

Open Settings → API Keys. The tab is visible to Business Unit admins only (it sits between Rate Cards and Trash). You can deep-link with ?tab=apiKeys, but a non-admin will just land on the default tab.

Create a key. Give it a name and confirm. The key is generated with a tlt_ prefix.

Copy it now. The plaintext key is shown exactly once, with a copy button. Talentino stores only a SHA-256 hash — there is no way to retrieve the key later. If you lose it, revoke it and mint a new one.

A key grants full Business Unit access — the same access as the admin who created it. There are no per-key scopes. The only control is revocation, so treat the key like a password and store it in a secret manager.

2. Make your first call

Send the key as a Bearer token. This imports one Resume from a URL:

curl -X POST https://app.talentino.example/api/v1/resumes \
  -H "Authorization: Bearer tlt_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "url": "https://example.com/cv.pdf" }'

A 201 response returns Talentino IDs you store on your side:

{
  "message": "Resume import accepted",
  "success": true,
  "data": {
    "resume_id": 12345,
    "candidate_id": null,
    "import_activity_id": 678,
    "import_activity_created": true
  }
}

candidate_id is null at import time — the candidate is resolved asynchronously by the pipeline. Poll the existing read endpoints (or watch for completion) using resume_id.

On this page