Wiza API review

What each Wiza API call costs

Wiza charges on what comes back, not on the request. Each endpoint draws on the same API credit balance, and a call that returns no data is free.

Every reveal is two steps. The POST returns an id, and the result arrives either from GET /api/individual_reveals/{id} or on the webhook URL set in your account. The finished response carries a credits object that splits the charge into email, phone and profile credits, so a pipeline can reconcile spend per row.

Wiza API pricing, plan by plan

Wiza API pricing is a prepaid credit balance, bought separately from the seat plans at $0.025 a credit with a 2,000 credit minimum.

The seat plans are for the Chrome extension and the app. Starter is $49 a user a month for 100 emails and 100 phones, Email is $99 for 500 emails, and Email + Phone is $199 for 500 of each. Billed yearly, Email is $990 and Email + Phone $1,990 a seat, with unlimited reveals and 2,500 exports a month.

Concurrency, a queue, and per-endpoint caps

Wiza API rate limits are set per endpoint. Individual Reveal accepts 15 requests a second, and behind that a concurrency limit decides how many reveals run at once: 5 on the Starter API tier and 15 or more on Enterprise API. Requests over that wait in a queue that holds 200 times your concurrency, so 1,000 on Starter and 3,000 at 15.

The limits are generous on paper and narrow in practice: 15 requests a second means little when five reveals run at once and a work email holds a slot for 25 seconds. The queue makes bursts safe, so the number to plan around is concurrency, and the tier that sets it is the one thing the pricing does not publish.

How to create a Wiza API key

A Wiza API key is created in the app under Settings, then API, by clicking New API Key, naming it and assigning the API User, which should match the account admin. Every request sends it as a Bearer token, and a missing, disabled or malformed key returns 401. The account needs API credits before a reveal will run.

The credential is ordinary; the scarcity is not. If three is a lifetime cap, rotating a leaked key spends one of them, so keep one key per environment and use the fair_key field, not extra keys, to separate customers.

What a Wiza API call looks like

A reveal takes one input, in this order of match quality: a LinkedIn URL, a full name and company domain, a full name and company name, or an email. Sales Navigator and Recruiter URLs are accepted as well as standard profile links. The webhook carries an x-auth-key header, a SHA256 hash of your API key, to verify it came from Wiza.

# 1. start a reveal for emails and phones
POST https://wiza.co/api/individual_reveals
{ "individual_reveal": { "full_name": "Jane Doe", "domain": "acme.com" },
  "enrichment_level": "full" }

# 2. collect it, or let the webhook deliver it
GET https://wiza.co/api/individual_reveals/{id}
# "credits": { "api_credits": { "total": 7 } }

Where the Wiza API documentation lives

The Wiza API docs live at docs.wiza.co, a Mintlify site with an OpenAPI spec, code samples in curl, JavaScript, Python and Ruby, and a plain-text index at llms.txt. The credit rules, the limits and the pricing are split across that site and three help center articles, which do not always agree.

The only published price is in the help center, not on the pricing page or the API landing page, which says to book a call. The list endpoints that older guides describe, with 2,500 profiles a request, are marked legacy in the current reference; new work goes through Individual Reveal in parallel.

Wiza's own integration walkthrough

Wiza publishes this on its own channel, so it is Wiza's account of Wiza, not ours. It is here because a rate card cannot show you the thing moving, and a few minutes of the product is faster than any paragraph on this page at telling you whether the shape of it fits yours.

Three and a half minutes from December 2025 on wiring Wiza into an n8n workflow with your own API key, which is the same key and the same credit balance this page prices. It is Wiza demonstrating its own node, so the match quality shown is Wiza's claim. The credit rules this page leans on are the ones in the API docs, not the ones on screen.

Published 8 December 2025 on Wiza, the channel Wiza's own pages link to, and read on 23 October 2026. Nothing in it is a source for a price or a limit on this page: every figure in the tables above comes from a Wiza page.

Strengths and limits

Wiza is priced like a pay-per-hit finder and sold like a seat product, and the API is the better deal of the two.

Read together, the two columns describe a good API sold awkwardly. The per-hit pricing and the miss-is-free rule make it cheap to test honestly; the separate wallet and the thin concurrency mean a team that already pays for seats should cost the API as a second product.

Who should actually buy this

Buy the Wiza API when your rows start from LinkedIn URLs and you want mobiles as well as emails, priced per hit with nothing to commit. At $0.05 an email and $0.125 a phone it is easy to bake off against the other finders on your own list.

Do not assume a seat plan covers it. A team on unlimited annual seats still buys API credits separately, so price the API on its own and decide whether the extension seats are still worth carrying.

At volume the constraint is concurrency, not credits. Five reveals at a time is a test bench; get the Enterprise API figure in writing before you build a pipeline that depends on it.

Two LinkedIn-first finders keep their API behind a sales conversation: Kaspr puts it on request from Starter, and ContactOut issues keys on its quote-only Team plan. The Kaspr alternatives and ContactOut alternatives pages set out where Wiza fits against each.

Before you build against it

Four things to settle first, each one read off Wiza's own pages. The ticks are remembered in this browser, so you can come back to a half-finished integration.

If Wiza is not the answer

Four providers in the Enrichment APIs listing that solve the same problem differently. Each one is a trade, and the trade is named.

The full set, organized by the reason people leave, is on the Wiza alternatives page.