Skip to content
GetAllAPIs
APIsPricingNetworkDocsPlaygroundFree tools
Dashboard Get started
APIsPricingNetworkDocsPlaygroundFree toolsDashboardGuidesFAQ Get started

Docs

  • Overview
  • Quickstart
  • API keys, spend limits and access levels
  • Running endpoints: envelope, response controls, max cost
  • Durable (async) requests and request history
  • Errors and billing semantics
  • Wallet and pricing
  • MCP server
  • Let an agent sign itself up
  • CLI and Python SDK
  • Audit log, retention, billing and feedback
  • Pagination and large results
  • Data sources and modes
  • SEO audit
  • Keyword gap report
  • Content brief
Docs / Durable (async) requests and request history

Durable (async) requests and request history

On this page
  • History
  • Retention

Add Prefer: respond-async to POST /v1/run/{endpoint_id} to get 202 Accepted at once, or Prefer: wait=N (max 90 s) to wait up to N seconds first. Without Prefer the call is synchronous.

A 202 carries Location: /v1/requests/{request_id} and Retry-After, and a snapshot:

{"ok": true, "request_id": "req_…", "endpoint": "seo.audit", "status": "queued",
 "created_at": "…", "expires_at": "…", "retry_after_seconds": 2}

Poll GET /v1/requests/{request_id}. status is queued, running, succeeded or failed. A succeeded snapshot has the normal run envelope in result; a failed one has error.code. Polling is free and never re-runs the paid call. Request ids are scoped to the wallet; others get 404.

With an Idempotency-Key, re-submitting while the job is active returns the same snapshot; after it succeeds the stored result is replayed.

A paid run is executed at most once. If the server restarts mid-job, the job is marked failed (interrupted) and the charge is not kept.

History

  • GET /v1/requests?limit=20&before=<cursor> — newest first across every key on the wallet: request_id, endpoint, key_prefix, status, http_status, cost_usd, items, latency_ms, input, created_at, error. Follow next_cursor (pass it as before); null means no more pages.
  • GET /v1/results/{request_id} — re-read a stored result for free, with the same fields/max_items/summary controls.

Retention

Successful output stays readable for 24 hours, then for the wallet's retention setting (0, 3 or 7 days; default 3): POST /v1/account/settings {"retention_days": 7}. After that result_expired: true (history metadata stays).

Plain Markdown for agents: /docs/durable-requests.md · index: llms.txt

Product

  • API catalog
  • Pricing
  • Site audit
  • Playground
  • Dashboard
  • Network

Free tools

  • All free tools
  • Title & description checker
  • robots.txt tester
  • Sitemap validator
  • hreflang checker
  • Heading outline
  • Structured data checker
  • Social preview
  • Indexability checker

Learn

  • Guides
  • Check reference
  • Use cases
  • Compare
  • Glossary

Developers

  • Docs
  • Quickstart
  • MCP server
  • Agent guide
  • llms.txt
  • OpenAPI

Company

  • About
  • FAQ
  • Changelog
  • Data sources
  • Contact
  • Security

Legal

  • Terms of Service
  • Privacy Policy
  • Refund Policy
  • Acceptable Use
  • Data Processing
GetAllAPIs © 2026 Mohamed Outerbah · [email protected]