Overview
Add Wiza to any ModuleX agent or workflow. Find, enrich, and verify B2B contact data with Wiza — prospect search, company enrichment, individual contact reveal (verified emails and phone numbers), and credit-balance lookup against the Wiza REST API (wiza.co/api).
Authentication
API Key Authentication
Authenticate using your Wiza API keyStep 1
Required Credentials
| Field | Description | Required | Format |
|---|---|---|---|
| Wiza API Key | Your Wiza API key from Settings -> API | Yes | - |
Available Actions
prospect_search — Search Wiza's database of prospects using person, company, and financial filters.
prospect_search — Search Wiza's database of prospects using person, company, and financial filters.
Parameters
Response
company_enrichment — Enrich a company by name, domain, LinkedIn ID, or LinkedIn slug with detailed firmographic data.
company_enrichment — Enrich a company by name, domain, LinkedIn ID, or LinkedIn slug with detailed firmographic data.
individual_reveal — Reveal a contact via LinkedIn URL, name + company/domain, or email. Starts the reveal and polls until it resolves. Uses 2 credits per valid email and 5 credits per phone, charged only on success.
individual_reveal — Reveal a contact via LinkedIn URL, name + company/domain, or email. Starts the reveal and polls until it resolves. Uses 2 credits per valid email and 5 credits per phone, charged only on success.
Parameters
Response
get_credits — Retrieve the remaining credits on your Wiza account.
get_credits — Retrieve the remaining credits on your Wiza account.
Response
Limits & Quotas
- Rate limit: ~30 requests/minute (43,200/day) per key.
- Credits: usage is metered in API credits — 2 credits per valid
email and 5 per phone on
individual_reveal, 2 credits per successfulcompany_enrichment;prospect_searchandget_creditsconsume no credits. Credits are charged only when data is returned. - Asynchronous reveals:
individual_revealstarts a reveal and pollsGET /api/individual_reveals/{id}until the status is terminal (finished/failed) or a 120-second window elapses. - Error model: non-2xx responses and timeouts are caught and
returned as
success=False+errorrather than raising. Plan for retries on the agent side based on the error string.