ApexVerify ACTION
ApexVerify - Email/Phone B2B Data Verification
Verify a single email address or phone number using ApexVerify. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's ApexVerify account once, then configure and run ApexVerify - Email/Phone B2B Data Verification from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "apexverify-unit-verification",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
apexverify: { authProvisionId: "apn_xxxxxxx" },
type: "Data Type",
unit: "Email or Phone to Verify",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "apexverify-unit-verification",
"configured_props": {
"apexverify": { "authProvisionId": "apn_xxxxxxx" },
"type": "Data Type",
"unit": "Email or Phone to Verify"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "apexverify",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "apexverify-unit-verification",
arguments: {
type: "Data Type",
unit: "Email or Phone to Verify",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
type Data Type | string | Which kind of contact data is being verified. Allowed values: email (verify an email address) or phone (verify a phone number). The value of unit must match this type — pass email here when unit is an email address, and phone when unit is a phone number. Required |
unit Email or Phone to Verify | string | The single email address or phone number to verify. Format must match type: for type=email, pass a full RFC 5322 email like jane.doe@example.com. For type=phone, pass a number in E.164 format with the leading + and country code — e.g. +14155552671 (US) or +442071234567 (UK). Hyphens and spaces are tolerated but not required. Only one address/number per call. Required |
targetCountry Target Country | string | Country against which the email or phone should be processed. Required |
targetAudience Target Audience | string | Optional target audience context for the verification. Accepted values include 1 for Agency / Consultants, 4 for Developers & Technical Leads, 8 for Founders & C-Level Executives, and 17 for Marketing & Sales Professionals. Optional |
targetMarketIndustry Target Market Industry | string | Optional market industry context for the verification. Accepted values include 18 for Construction, 29 for Finance and Insurance, 42 for Health Care and Social Assistance, 46 for Information, and 91 for Retail Trade. Optional |
targetObjective Target Objective | string | Optional campaign or business objective context for the verification. Accepted values include 4 for Customer Acquisition / Sales, 6 for Lead Generation (Top/Mid-Funnel), 12 for Sales-Ready Leads, and 16 for Website / App Traffic Acquisition. Optional |
useAccountCache Use Account Cache | boolean | Use previous verification results from your ApexVerify account cache when available. Optional |
maxAccountCacheBackoff Max Account Cache Backoff | integer | Maximum number of days to look back in account cache. Min: 1. Max: 180. Optional |
useGlobalCache Use Global Cache | boolean | Use anonymized global cache results when available. Optional |
maxGlobalCacheBackoff Max Global Cache Backoff | integer | Maximum number of days to look back in global cache. Min: 1. Max: 180. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- apexverify-unit-verification
- Version
- 0.0.2
- App
- ApexVerify
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗