AgencyZoom API: Automating Lead Follow-Up and Renewals
With Carly connected to AgencyZoom, a lead that arrives at 7:40pm does not have to wait until Thursday morning. Speed-to-lead is the whole game in this business, and Carly can act from the inbox immediately even though AgencyZoom itself does not push new events through webhooks.
Carly doesn’t wait for AgencyZoom to tell it. It triggers on the email, which is where most leads land first anyway:
- Answers the lead in minutes, at 7:40pm, from your address — qualifying questions, your voice, before the prospect has opened the next carrier’s site.
- Runs the quote follow-up sequence — the second, third, and fourth touch that produces most bound policies and that nobody has time to send by hand.
- Chases X-dates and renewals off the calendar, which doesn’t need AgencyZoom’s cooperation at all.
- Writes it back into AgencyZoom through your API key, so the CRM stays current without anyone typing into it.
You describe it in plain English — “when a lead email comes in, reply within five minutes, then follow up on day 2, 5, and 12 unless they respond” — and Carly interviews you, then builds it. AI agents start at $35/month, and workflow steps that don’t use AI run free and unlimited. Paste your key on carlyassistant.com/integrations.
The rest of this is the honest state of the AgencyZoom API — what you can get, what you can’t, and the one genuinely odd limit worth designing around.
What agencies actually automate with it
Speed-to-lead is the whole game in this business, and it’s the thing AgencyZoom makes hardest to automate — because nothing gets pushed to you.
What works from your inbox and calendar, and is usually faster anyway:
- Speed-to-lead. Most leads hit your email before or alongside AgencyZoom. Responding off the email gets you there in minutes rather than waiting on the next check of the API.
- Quote follow-up sequences — the second, third, and fourth touch that produces most bound policies and that nobody has time to send by hand.
- Renewal and X-date outreach, which is calendar-shaped and doesn’t need AgencyZoom’s cooperation at all.
What works by checking on a schedule:
- Stalled leads sitting in a stage too long, surfaced before they go cold.
- Service tickets aging past your own standard.
- Daily pipeline summaries to the principal without anyone building a report.
The rest of this page explains why the schedule-checking side is more constrained than you’d expect, and how to work inside it.
Getting credentials
Integrations page → click Zapier → click “Show API Key”. The popup reveals both an API key and an API secret. Same path for Make.
No tier gate appears anywhere. AgencyZoom’s pricing lists Essential at $149, Growth at $199, and Pro at $349, with Zapier integration on all three. No plan requirement, no role requirement, no partner agreement.
This is not a HawkSoft situation. Insurance is a vertical where documentation exists but credentials turn out to be partner-only — HawkSoft is the standing example. AgencyZoom isn’t that. An ordinary paying customer gets their own credentials.
One correction to something widely repeated: AgencyZoom was acquired by Vertafore in November 2021, not by EZLynx or Applied Systems. EZLynx shows up on AgencyZoom’s integrations page as a Zapier-powered partner, which is probably where the confusion starts. No partner gate came with the acquisition.
The real documentation is the OpenAPI spec at https://app.agencyzoom.com/openapi/agencyzoom.yaml — 313KB, linked from the site footer. The /openapi/ portal itself is a JavaScript Swagger shell with nothing readable in it, so go straight to the YAML.
Three overlapping auth concepts
This is the messiest part of the API, and worth understanding before you build.
The spec’s only declared security scheme is JWT bearer. You get one by posting a username and password — an actual login — to /v1/api/auth/login.
Then the spec adds this: “the permissions afforded to the caller are the same as those for the logged in user. Therefore, the user name used for the integration has to be the agency owner if the integrated applications would like to access all the functionalities.”
So a full-access integration effectively requires the agency owner’s own credentials. There’s no scoping, no independent revocation, and it breaks when the owner changes their password or enables MFA. That’s a meaningful operational risk to raise with a principal before you ask for it.
Meanwhile, the in-app credential surfaced for Zapier and Make is an API key plus secret — a different thing. And exactly one endpoint out of 114, policy creation, wants an X-Api-Token header instead.
Three concepts, no page reconciling them.
Base URL is https://api.agencyzoom.com, version v1, and the spec says there’s only one version. Note that api.agencyzoom.org is an unrelated product.
Broad write coverage
114 operations across 98 paths — 45 POST, 38 GET, 21 PUT, 10 DELETE. Full CRUD on:
- Leads — create, batch create, update, delete, rename, change status and stage, move to sold, notes, files, quotes
- Customers and contacts, including batch creation
- Opportunities, including drivers and vehicles with link and unlink
- Policies — create, update, update status, update tags, and endorse
- Tasks — create, complete, reopen, batch delete
- Service tickets
Reference data — carriers, pipelines and stages, lead sources, employees, CSRs, custom fields, tags, loss reasons — is read-only.
One genuinely unusual capability: read and write access to email and text threads. Most agency CRMs don’t expose messaging at all.
No outbound webhooks, and polling is awkward
There is no publicly documented outbound webhook API. The spec has no webhooks block and no callbacks. Composio’s AgencyZoom toolkit independently reports zero triggers across 99 tools, which is corroborating — that catalog is generated from the vendor API.
AgencyZoom’s “webhook” feature is inbound only. Its Web Lead Integration creates “a unique URL code for your lead vendor to send data to” — you POST leads in. You cannot register a URL to receive events out, and it’s restricted to a picklist of supported vendors rather than arbitrary endpoints.
Events do exist, but only through Zapier — six triggers:
- Lead Created
- Lead Stage Change
- Lead Status Change
- New Policy Sold
- Service Request Created
- Service Request Status Change
Whether these are instant or polled isn’t documented. Given there’s no webhook-registration endpoint anywhere and Composio sees no triggers, polling is the likely answer.
Which makes rolling your own detection harder than it should be. The leads list endpoint restricts sorting to an enum of first name, last name, last stage-entry date, and last activity date — there is no create-date sort. Filters offer last-activity date ranges but no create-date range. So “new leads since X” has no clean primitive; you’re reconstructing it from activity dates.
Combine that with 30 calls a minute during business hours and the polling story is genuinely constrained. The overnight window doubling to 60 stops being a curiosity and starts being where your sync has to live.
The undocumented API hiding in the spec
Worth knowing if you’re doing anything high-volume: 28 of 30 Enterprise_* schemas in the spec are orphans. Full batch create, update, and delete models for customers, leads, policies, quotes, and unsubscriptions exist with no corresponding paths.
Several carry a meta field described as “The metadata will be passed to the webhook along with the generated IDs.”
So there is an async batch API with callbacks — it’s simply not documented publicly. If you’re moving serious volume, that’s the thing to ask Vertafore about rather than trying to batch through the 30-per-minute front door.
Four more traps
- The rate limit has no error contract. Across all 114 operations the spec documents only 200, 400, 404, and 500 — not a single 429. The limit is stated in prose with nothing describing what breaching it returns, though it does fire in practice.
- Pages are 0-indexed, and maximum page size varies by endpoint — 100, 200, or 500, with no consistency.
- Lead creation needs five IDs resolved first — pipeline, stage, lead source, assignee, and country. Each is a lookup call, and each one spends your rate-limited budget before you’ve created anything.
- Wrong HTTP method returns 404, not 405, which will send you hunting for a missing endpoint that’s actually right there.
Minor but telling: the sole production server in the spec is labelled “Mobile test server.”
AgencyZoom ships no AI of its own
Worth stating clearly, because the internet says otherwise. There are no AI mentions across AgencyZoom’s homepage, its six product pages, Vertafore’s product page, the acquisition release, or any of the 14 release notes from January 2025 through July 2026. There’s no AI page, no named assistant, nothing shipped and nothing announced.
Several SEO-driven sites claim AgencyZoom has AI lead scoring, outreach copywriting, or X-date automation. Every primary source contradicts them.
The AI on AgencyZoom’s integrations page is all third-party partners — LeO, GAIL by LULA, and seeb.ai among them.
Getting the event to do something
A lead landing, a stage changing, a policy selling — these are the moments where an agency either follows up in minutes or loses the quote. AgencyZoom will not push you any of them.
Handing that to an AI assistant doesn’t solve it either.
The unattended-work gap closed in 2026: ChatGPT Scheduled Tasks and Claude Cowork both run on their own. The remaining gap is what starts them. These run on a timer, not in response to an event in your apps, so "when this happens, do that" is still outside what they do.
“Summarize this month’s close rate by producer” is well within what ChatGPT or Claude will do with an AgencyZoom export. “Text the prospect within five minutes of the lead arriving” is not — and since nothing gets pushed, something has to be watching.
That’s the case for triggering off the inbox rather than the API, which is where this piece started. But two details are worth adding now that you’ve seen the constraints:
- Where Zapier’s triggers do cover you — lead created, stage or status change, policy sold, service request — Carly fires on those directly rather than polling.
- Where they don’t, the polling is tuned to the limits above. No create-date sort and no create-date filter, against 30 calls a minute, is exactly the kind of awkward budget that punishes a naive loop — and shifting bulk work into the 60-per-minute overnight window is the sort of thing worth not doing by hand.
Scope the account you generate credentials from deliberately, given the auth model.
Frequently Asked Questions
What is the AgencyZoom API rate limit?
30 calls per minute during the day and 60 per minute between 10PM and 4AM Central, per AgencyZoom’s own OpenAPI spec. Note the spec documents no 429 response, so nothing describes what a breach returns.
Do I need a specific AgencyZoom plan for API access?
No. Zapier integration is listed on all three published tiers — Essential at $149, Growth at $199, and Pro at $349. The API key and secret are revealed from the Integrations page with no partner agreement or approval.
Does AgencyZoom have webhooks?
Not outbound. Its webhook feature is inbound only — a unique URL your lead vendors post data to. There’s no way to register an endpoint to receive events. Six triggers exist through Zapier covering leads, policies, and service requests, but they’re likely polled rather than instant.
Who was AgencyZoom acquired by?
Vertafore, in November 2021. EZLynx and Applied Systems are frequently named by mistake — EZLynx appears on AgencyZoom’s integrations page as a Zapier partner, which is the likely source of the error. No partner gate followed the acquisition.
Does AgencyZoom have AI features?
No. No AI features appear in any AgencyZoom or Vertafore primary source, including every release note from January 2025 through July 2026. Third-party sites claiming AI lead scoring or outreach copywriting are contradicted by the vendor’s own material. The AI on its integrations page belongs to partner products.
How do I detect new AgencyZoom leads via the API?
There’s no clean way. The leads list endpoint has no create-date sort and no create-date range filter — sorting is limited to names and activity dates. You reconstruct new-lead detection from last-activity dates, within a 30-call-per-minute budget.
More: AI agents for ops · Best AI workflow automation tools · Best AI agents for productivity
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
