Grid82
grid82.comJoin the waitlist
DevelopersIdempotency

Retries and idempotency

Use the Idempotency-Key header on POST writes so retried requests replay the original result safely for 24 hours without duplicates.

Networks drop responses and automation scripts retry. Passing an Idempotency-Key header prevents duplicate record creations or side effects when a POST request is retried.

Terminal
curl -X POST "https://your-suite.grid82.app/your-app/v1/tables/tbl_8fj3kq2wmv5d/records" \
  -H "Authorization: Bearer $GRID82_TOKEN" \
  -H "Idempotency-Key: 6f1c2b8e-1d2a-4f0e-9a51-2f1d7e0c3b44" \
  -H "Content-Type: application/json" \
  -d '{"records":[{"Name":"Meridian Annual Support","Amount":24000}]}'

Idempotency rules

ScenarioServer behaviour
First time seeing Idempotency-KeyExecutes request and caches response for 24 hours
Same key + identical request body within 24 hoursReturns original response with header Idempotency-Replayed: true without re-executing
Same key + different request method, path, or bodyRejects with 409 conflict
  • Key format. Any unique string up to 255 characters (a UUID per logical operation is recommended). Keys are scoped by plane, caller, and operation.
  • Permission check on replay. Cached responses verify that the caller’s rights still cover the replayed answer before returning it.
  • Methods. POST endpoints documented with Idempotency-Key support replay caching. Repeating PUT, PATCH, or DELETE is already idempotent on its own.

Retry strategy

  • Do retry. 429 (rate_limited), 500 (internal), and network timeouts, using exponential backoff and the same Idempotency-Key.
  • Do not retry. 400/422 validation errors, 401/403/404 authorization errors, 402 quota errors, or 2xx saves that succeeded with warnings.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Grid82 documentation and read it in full, instead of answering from memory.

https://grid82.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://grid82.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.