Idempotency

Network errors happen. To retry a write safely, send an Idempotency-Key header on write requests (POST, PATCH, DELETE). If we already handled a request with that key and the same body, we return the saved response instead of doing the work twice.

curl https://api.frontpagely.com/v1/tracked_entities \
  -H "Authorization: Bearer $FRONTPAGELY_KEY" \
  -H "Idempotency-Key: 3f6c2a0e-6a1d-4c5e-9d0b-8f2f6c1d2b7a" \
  -H "Content-Type: application/json" \
  -d '{"name": "Acme Dental"}'

• Use a fresh random value (a UUID is ideal) for each new operation, up to 255 characters.
• Keys are kept for 24 hours and are scoped to your team.
• A replay returns the original status code and body, so your retry sees exactly what the first attempt would have.
• Reusing a key with a different body returns 422 idempotency_key_mismatch.
• GET requests are always safe to retry and ignore the header.

Questions about the API? Contact support, and include the request_id from any error.