Skip to content

Pagination and idempotency

Cursor pagination and Idempotency-Key for safe retries.

1 min read 2 sections

Cursor pagination#

GET /api/v1/links is paginated with a cursor. limit is normalized to the 1–100 range. The meta field in the response contains hasNext, nextCursor and the total.

list-links.sh
curl "https://api.beklio.com/api/v1/links?limit=50&cursor=NEXT_CURSOR" \
  -H "Authorization: Bearer bk_live_…"

The page parameter is accepted for backward compatibility, but new clients should use the cursor. A tampered or malformed cursor returns 400.

Idempotency-Key#

Idempotency-Key is supported on create, update, delete and all route sub-resources.

  • Same key and the same payload: the first response is replayed as is, and the quota is not counted twice.
  • Same key, different payload: 409 Conflict.

Generate a new key for every logical operation (e.g. a UUID) and retry with the same key after a network error.

Is something missing or wrong? Write to the support team; including the X-Request-Id value from the response speeds up the fix.