Idempotency

If a request times out you cannot know whether it worked. Send the same Idempotency-Key again and you get the first answer, not a second check.

Docs menu

curl

curl -X POST "https://pressprove.com/api/v1/checks" \
  -H "Authorization: Bearer $PRESSPROVE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: nightly-2026-11-02-001" \
  -d '{"pages":["https://news.example.org/2026/11/live-link-roastery"],"client_domain":"example.com"}'
  • The key is 1 to 255 printable ASCII characters, such as a UUID or a job number. Anything else answers idempotency_key_invalid.
  • Every POST accepts it. It is required on POST /releases, which spends money. It is recommended on the other POSTs that create something.
  • A key belongs to your account, to the mode and to the API key you used. It is remembered for 72 hours.

What happens

You sendYou get
A new keyThe work is done and the answer is kept with the key.
The same key and the same requestThe kept status and body again, with the header Idempotent-Replayed: true. Nothing is done twice and nothing is charged twice.
The same key and a different request422 idempotency_key_reused. Use a new key for a new request.

Two requests are the same when the method, the endpoint, the ids in the path and the body (read as JSON, in any key order) match. Failed requests are kept too, so a replay of a 400 is the same 400. Authentication errors, rate-limit answers and server errors (401, 429, 5xx) are not kept, so you can retry them.

How to use it

  • Make the key once per piece of work, before the first try, and send it on every try of that work.
  • Do not reuse a key for different work.
  • In the console, a form carries a key of its own, so a double click makes one object.