Idempotent requests

Safely retry write requests with the Idempotency-Key header.

Idempotency lets you safely retry a request without performing the same operation twice — useful when a network error leaves you unsure whether the first attempt succeeded.

To make a write request idempotent, send a unique Idempotency-Key header:

bash

curl https://api.getmeonline.io/v1/... \
  -X POST \
  -H "Authorization: Bearer $GETME_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{}'

If a request is retried with the same key, the API returns the result of the original request instead of running the operation again.

Use a unique key per logical operation, and reuse the same key only when retrying that exact operation. Keys must be 16-128 characters and may contain letters, numbers, ., _, :, and -.

Getme stores idempotency results for the replay window, currently 24 hours. If the same key is reused with a different method, path, or request body, the API returns 409 with error_code: "DEVELOPER_IDEMPOTENCY_CONFLICT".

Read-only requests do not need an idempotency key. Mutating endpoints that require one document the Idempotency-Key header in the API reference.