Delete Batch
Permanently delete one ApexVerify batch by its exact UUID. Deletion is irreversible and unavailable while the batch is processing; verify the target batch first and deliberately set confirm_deletion=true.
ApexVerify validates and normalizes email addresses and phone numbers individually or in batches to improve contact-data quality.
Permanently delete one ApexVerify batch by its exact UUID. Deletion is irreversible and unavailable while the batch is processing; verify the target batch first and deliberately set confirm_deletion=true.
Export a completed batch as structured JSON for analysis or as a downloadable XLSX workbook. This reads existing results and does not consume verification credits.
Return the connected ApexVerify account's available email and phone verification credit balances. Use this before any credit-consuming verification.
Get an ApexVerify batch's status, metadata, parsed-content counts, estimated verification cost, parameters, and final statistics. Repeat this call to monitor preparation or verification.
Launch paid verification for a prepared batch. This consumes the batch's estimated net email or phone credits and can fail when credits are insufficient. First inspect Get Batch Details and Get Account Credits, then deliberately set confirm_credit_spend=true.
List verification batches, optionally restricted by creation time, one offset-controlled page at a time.
Normalize email addresses or phone numbers from a line-delimited TXT file without performing verification or consuming verification credits.
Start or repeat asynchronous parsing, deduplication, format cleanup, and verification-cost calculation for an uploaded batch. This idempotent action does not launch paid verification. Poll Get Batch Details until the batch is ready for verification.
Create an ApexVerify verification batch from a line-delimited TXT file. Uploading does not consume verification credits; verification starts only when the batch is launched separately.
Verify one email address or phone number in real time. This consumes the corresponding prepaid verification credit; cache hits may receive a partial refund. Check account credits first and deliberately set confirm_credit_usage=true.
The ApexVerify integration connects your Dench AI CRM directly to ApexVerify, so agents can read and act on your ApexVerify data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
10 actions are available for agents to invoke on your behalf. Every call runs through ApexVerify's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find ApexVerify and click Connect — you'll authorize access through ApexVerify's own sign-in flow. No API keys or code required.
Ask an agent to use ApexVerify in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench ApexVerify integration connects your AI CRM to ApexVerify, so AI agents can work with your ApexVerify data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The ApexVerify integration currently exposes 10 actions, including Delete Batch, Export Batch Results, Get Account Credits, Get Batch Details, Launch Batch Verification, and List Batches. Agents invoke them on your behalf from chat or from automations.
No. You connect ApexVerify from your Dench workspace using ApexVerify's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through ApexVerify's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the ApexVerify connection from your workspace settings at any time.