Langsung ke konten

API

Idempotency.

Retry a POST after a timeout without creating the candidate or the invitation twice.

Terakhir diperbarui 19 November 2026

Dokumentasi developer hanya tersedia dalam bahasa Inggris.

Send an Idempotency-Key

POST /v1/candidates, POST /v1/invitations and POST /v1/invitations/{id}/resend accept an Idempotency-Key header: any unique string up to 200 characters, such as a UUID you generate per operation. Keep it for the retries of that one operation.

curl -X POST https://api.testee.ai/v1/candidates \  -H "Authorization: Bearer $TESTEE_API_KEY" \  -H "Content-Type: application/json" \  -H "Idempotency-Key: 8e0f6c1a-2b7d-4d0e-9a51-3c6f2e9b7d40" \  -d '{"name":"Ada Lovelace","email":"ada@example.com"}'

What a retry gets

Retry with the same keyResponse
and the same body, after the first request succeededThe first response again; nothing new is created
and the same body, while the first is still running409 A request with this Idempotency-Key is already in progress
and a different body422 Idempotency-Key was used with a different request body
after the first request was refused (a 4xx such as 400, 404 or 409)Runs again: refusals aren't stored
after a 5xx or a timeout409 for up to 60 seconds, then it runs again. A candidate or an invitation the first request already created comes back instead of a second one (or a 409)
  • 24 hours. A key is remembered for 24 hours, per company: a retry sent with another of your API keys (after a rotation, say) gets the same answer. After that the same key starts a new request. Use a new key for each new operation.
  • Without a key a POST runs every time. A second candidate with the same email is still refused (409), but a second invitation would be created, and a second resend would send another link.