BizVerify in Zapier.
There is no BizVerify app in the Zapier directory — and you don't need one. One Webhooks by Zapier POST verifies a business against the current official record; a Catch Hook collects the results that finish in the background.
The two-Zap pattern
Zapier has no loop construct, so a Zap can't poll a job until it finishes. Hand BizVerify a webhook_url instead — Zap 2's Catch Hook — and branch Zap 1 on the immediate response.
Zap 1 Trigger (e.g. new CRM lead)
→ Webhooks by Zapier · Custom Request
POST /v1/verify body includes webhook_url = Zap 2's Catch Hook URL
→ Paths on response "status"
├─ completed (HTTP 200, data inline) → update the CRM record now
└─ pending (HTTP 202, job_id) → end here; Zap 2 takes over
Zap 2 Webhooks by Zapier · Catch Hook
← BizVerify POSTs verification.completed / .failed / .refunded
→ Paths on "event"
→ Find CRM record by entity_name → update itZap 1 sends
POST https://api.bizverify.co/v1/verify
X-API-Key: bv_live_...
Content-Type: application/json
{
"entity_name": "Acme Corporation",
"jurisdiction": "us-fl",
"verification_level": "quick",
"webhook_url": "https://hooks.zapier.com/hooks/catch/1234567/abcd123/"
}Zap 2 receives (async results only)
{
"event": "verification.completed",
"job_id": "job_abc123",
"jurisdiction": "us-fl",
"entity_name": "Acme Corporation",
"status": "completed",
"data": {
"entity_name": "ACME CORPORATION",
"entity_type": "corporation",
"status": "active",
"jurisdiction": "us-fl",
"formation_date": "2015-03-12",
"confidence": 95
},
"credits_charged": 1,
"credits_refunded": false,
"completed_at": "2026-04-02T12:00:00.000Z"
}A 200 response never produces a webhook. When a verification completes inline, the result is already in Zap 1 — the Catch Hook only hears about work that finished in the background. That's why Zap 1 branches on status instead of ending at the POST. It also means your update step exists in both Zaps. That duplication is the honest cost of the callback pattern.
The payload echoes entity_name and jurisdiction exactly as you sent them, and job_id matches the 202 response. Zap 2 re-finds your record with a Find Record step keyed on the echoed entity_name.
One endpoint, two response shapes
Some verifications return inline; others complete in the background. POST /v1/verify tells you which happened:
200 · status: "completed"
The full result is in data, right in Zap 1's response. Act on it in the completed Path — no webhook will follow.
202 · status: "pending"
You get a job_id; the result arrives at your webhook_url when the job finishes, fails, or is refunded.
Prefer one Zap? Use a Delay instead of a Catch Hook.
After the pending Path, add Delay by Zapier, then GET /v1/verify/status/{job_id}. Most jobs complete within 10–30 seconds, so a one-minute delay covers nearly all of them — and the whole flow keeps the trigger record's context, so there's nothing to re-find. The trade-off: a job that outruns your delay is missed. The Catch Hook pattern is the guaranteed-delivery upgrade; deliveries retry with backoff (see webhook delivery details).
What you need
A paid Zapier plan
Webhooks by Zapier — both the Catch Hook trigger and the POST action — is a premium app, available on Professional, Team, and Enterprise.
A BizVerify API key
Sent as the X-API-Key header on every request. Free on signup, 50 credits included, no card.
Zap 2's Catch Hook URL
Create Zap 2 first, copy its Catch Hook URL, and paste it into Zap 1's webhook_url field.
Delivery mechanics — retries, timeout, response requirements — are in the webhooks reference.
What a verification is — and isn't
BizVerify answers one question well: does this legal entity exist, and what does its registry record say right now?
Verifies
- Confirms the entity is registered with the official government registry
- Returns the current registry status (active, dissolved, suspended, etc.)
- Returns canonical entity name, type, and jurisdiction id
Does not verify
- Verify solvency, credit, or financial standing
- Verify beneficial ownership or employment
- Screen against sanctions lists
- Prove the entity isn't a shell
If Zapier isn't the right fit
The premium-app requirement is Zapier's, not ours. The same verification runs anywhere that can make an HTTP request.
Wire it into your next Zap.
Fifty free credits on signup. No card. The same key works in Zapier, n8n, and every integration on this site.
Read the webhooks reference →