Reference & Lookup Data · Integration
Wiza
Add Wiza to your product for your customers, and give your AI agents governed access to it.
Wiza's REST API lives under wiza.co/api with a bearer API key. Work is asynchronous: you create a prospect list from a LinkedIn Sales Navigator or Recruiter search, then poll the list until its status reports finished before fetching contacts, because fetching early returns an incomplete set. Prospect search returns match counts first so you can size a list before spending anything, and credits are consumed for revealed emails and phone numbers rather than for the search itself. Individual reveal covers the single person case and verifies live instead of serving a cached row, so the same request can return a different result a month later. As a lookup service there is nothing to write back: results are query outputs, not a system of record. fastn stores each customer's own Wiza key, tracks list job state and keeps credit spend attributable to the tenant that caused it.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Wiza key so enrichment runs on their credits rather than yours
Enrich a newly created contact in your app with a verified work email and direct dial at the point of creation
Build a list from a saved search and import the finished contacts into your product once the job reports complete
Show remaining credit consumption per customer so account owners can see what enrichment is costing them
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Have an agent size a prospect search before running it, reporting the match count and estimated credits rather than revealing straight away
Let an agent reveal contact details for a named person only when a user asks, with each reveal audited per tenant against that tenant's credits
Ask an agent to check whether a queued list has finished processing and report how many contacts came back with a verified email
Example prompt
How many heads of engineering at UK fintechs under 200 people would this search return, and what would revealing them cost?
Set up Wiza in 4 steps
- 01Enable the Wiza connector from your fastn dashboard.
- 02Have each customer authorise their own Wiza account, so calls run under their credentials rather than a shared key.
- 03Decide which lookups, results and reports your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Wiza integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Wiza integration without building it. Your customers connect their own Wiza account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Wiza update is not your on-call problem.
- One integration serves your product and your agents. The same governed Wiza connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Clearbit
APIVoidOften used alongside
Tools the same teams tend to run next to Wiza, across other categories.
Salesforce
HubSpot
Notion
SnowflakeWiza integration FAQ
How do I add a Wiza integration to my product?
Enable the Wiza connector in your fastn dashboard, then let each customer authenticate their own Wiza account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Wiza client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Wiza account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Wiza account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Wiza integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Have an agent size a prospect search before running it, reporting the match count and estimated credits rather than revealing straight away
Who maintains the Wiza integration?
fastn does. When Wiza changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a Wiza lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Wiza results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Wiza is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Wiza integration?
A common starting point: let a customer connect their own Wiza key so enrichment runs on their credits rather than yours. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Wiza integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Wiza does not change your per-connector cost. You can start free with 3 connected accounts.
Add Wiza to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.