The AuditZap REST API for Agencies Is Live

If you audit one site, the dashboard is the right tool. If you audit forty client sites every month, it is not. You want a script that walks a list, starts the audits and drops the numbers into a sheet.

That is what the AuditZap REST API is for. It is live today for every Agency account, and the full reference is on the API docs page.

Why an API

An agency running audits for clients needs three things the dashboard alone does not give.

The first was bulk audits. A new client brings a list of sites, or you want a baseline for your whole portfolio. Typing each URL into a form works for five sites. It does not work for fifty.

The second was getting results out. Scores and failing checks are useful in AuditZap, but account managers live in spreadsheets and dashboards. The API returns every result as JSON, and exports a complete audit as CSV or plain text.

The third was white-label PDFs on demand. Your branding is already on the PDF reports. Now a script can fetch the PDF for a finished audit and attach it to a client email or a project folder.

What it does

You create an audit with a POST request that takes a URL and, if you like, a page limit. The response comes back straight away with an audit id and a status of queued. Without a page limit, the audit crawls up to 250 pages, the Agency cap.

Then you poll that audit. Its status moves from queued to running to complete or failed. When it is complete, the response holds the score, the summary and every check result, grouped into Critical, Performance, SEO, Quick Wins and AI Visibility.

You can also list your audits, newest first, filtered by URL or status and paged with a cursor. Finished audits export as CSV, text or PDF. A usage endpoint tells you how much of today's allowance is left.

Here is the create call from the docs:

curl -s -X POST https://auditzap.io/api/v1/audits \
  -H "Authorization: Bearer $AUDITZAP_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com", "maxPages": 100}'

And a loop that polls until the audit finishes:

while true; do
  body=$(curl -s https://auditzap.io/api/v1/audits/$AUDIT_ID \
    -H "Authorization: Bearer $AUDITZAP_KEY")
  status=$(echo "$body" | jq -r '.data.status // empty')
  if [ "$status" != "queued" ] && [ "$status" != "running" ]; then echo "$body"; break; fi
  sleep 10
done

The docs also have a longer loop for a whole list of sites, which waits out rate limits and collects one CSV per audit.

What an API audit does not do

An API audit is an ordinary audit. It appears in your dashboard and uses the same crawler and the same checks. Three things differ.

It does not send the completion email, because your script is already waiting for the result. It does not join weekly monitoring, so a bulk run can never push out the sites you watch from the dashboard. To monitor a site weekly, run it once from the dashboard. And it counts toward your plan's daily audit allowance, which the API and the dashboard share.

Limits in plain words

Each key can create up to 10 audits a minute and make up to 120 read requests a minute. PDF downloads have a lower limit of their own, because they take longer to build.

If you hit a rate limit, the 429 response carries a Retry-After header with the seconds to wait. If a 429 has no Retry-After, today's allowance is used up. The usage endpoint shows the allowance and how much of it is left.

How to get a key

Open Settings, then API keys, and create one. The key is shown once, so copy it somewhere safe. You can hold up to 5 active keys, for example one per tool or per team member, and you can revoke any of them at any time. A revoked key stops working at once.

Keys work while your account is on the Agency plan. If you are not on Agency yet, the pricing section shows what each plan includes.

This is v1

We wanted to ship something small that works well. We would rather learn from real use than guess.

Some things we are considering: webhooks, so you do not have to poll, batch create, so one request starts many audits, and a cross-audit export, so one file covers a whole client list. None of these is promised. Which one matters to you, if any?

If you build something with the API, or hit something it cannot do, tell us. The API docs are the place to start, and the Help page inside the app reaches us directly.