Skip to main content
Prefetch is a plain HTTPS API with an X-API-Key header, so every no-code tool that can make an HTTP request can use it. These guides give the exact configuration for the jobs people use them for:

Clay

HTTP API columns that resolve, enrich and classify every row.

n8n

Four workflows to paste straight into your editor.

Zapier

Enrich new CRM records and name transactions with Webhooks by Zapier.

Make

Scenarios built on the HTTP “Make a request” module.

​
Before you start

  • Your API key goes in an X-API-Key header. Create one on the dashboard. Treat it like a password: use your tool’s credential store rather than pasting it into a field everyone can read.
  • Concurrency. Every plan limits how many requests run at once — 1 on Free, 10 on Starter, 50 on Pro. Tools that run rows in parallel (Clay, n8n, Make) should stay at or under that; a request over it waits a few seconds for a slot, then gets 429 with error_code: CONCURRENCY_LIMITED.
  • Errors tell you whether to retry. Every error body carries error_code and retryable. Retry retryable: true (busy, timeouts, rate limits) after a pause; don’t retry retryable: false (an invalid domain, a site that does not exist). See Errors.
  • Failures are free. A request that fails is never charged, so retrying one costs nothing until it succeeds.