Safe retries
When a connection drops, you cannot know whether your order went through. So send it again: for 7 days the same key means the same order, and it is charged once.
How it works
POST /orders needs an Idempotency-Key header: up to 200 ASCII characters with no spaces, which you make up and keep with your own record of the order. A UUID works well. Use a new key for a new order.
curl -X POST "https://api.talismanleads.io/v1/orders" \
-H "Authorization: Bearer tl_live_your_key_here" \
-H "Idempotency-Key: crm-export-2026-11-05" \
-H "Content-Type: application/json" \
-d '{"checker":"whatsapp_status_detection","entries":["+14155550142","+12125550187"]}'What you get back
201 and the new order.200, the same order, and Idempotent-Replay: true. Nothing more is charged, even if the price has changed since.order_status_unknown or rate_limited.409 idempotency_conflict. Nothing is placed.insufficient_balance409 price_changed, and a new key orders at the new price.When you do not know
Any answer that is lost, order_status_unknown, and an answer that is not JSON, such as a gateway's 502 or 504, all mean the same thing: repeat the request with the same key to learn the true state. It never charges twice. Never make a new key because a request timed out or failed: that is a new order, and it is charged.
Wait a minute between repeats. If it still answers order_status_unknown after a few minutes, stop and contact support with the request_id. Do not make a new key.
How long a key lasts
A key is remembered for 7 days from when it was first sent. After that the same key places a new order, so retry within a few days and keep a new key for each new order.