API Reference

Idempotency

Safely retry POST requests with an Idempotency-Key header.

Network failures happen. Without idempotency keys, a flaky retry can create the same job twice or move the same candidate twice. With them, retries are safe.

Recipe

Generate a unique key per logical operation — UUIDv4 is fine. Persist it client-side until you are sure the call succeeded.
Send it as the Idempotency-Key header on the request.
If the network fails, retry with the same key. Ceevee returns the cached response without re-running the operation.
Reuse keys only for the same operation. The API hashes the request body and rejects mismatched re-uses with 409 conflict.

Example

curl -X POST https://api.ceevee.cc/v1/jobs \
  -H 'Authorization: Bearer ceevee_sk_live_…' \
  -H 'Idempotency-Key: 7d8e3f2c-1a4b-4c2d-9b3e-9c8a1f4d5e7f' \
  -H 'Content-Type: application/json' \
  -d '{ "name": "Senior Frontend Engineer" }'

Cache window

Cached responses are returned for 24 hours after the first call. After that the key is freed and may be reused for a new operation.