Idempotency

Time Hive is built on a defensible ledger. To prevent accidental double-counting (e.g., if Zapier retries a failed webhook delivery), our API supports idempotency.

How It Works

If you provide an idempotency_key in your JSON payload, Time Hive guarantees that only ONE event with that key will ever be recorded for that task.

{
  "status": "processed",
  "idempotency_key": "exec_12345abcde"
}

If we receive a second request with "idempotency_key": "exec_12345abcde", the API will respond with a 200 OK status and a message indicating the event was already processed. It will not create a duplicate row in the ledger, and your time-saved metrics will remain accurate.

Auto-Generation

If you do not provide an idempotency_key, the API will automatically generate a random UUID for you upon ingestion. However, this means retries will result in duplicates. We strongly recommend passing a unique execution ID from your automation platform.