1shot API email verification with BillionVerify
1shot API is a developer tool for sending HTTP requests and automating API interactions without building custom infrastructure. Pairing it with BillionVerify adds email verification to any pipeline — validate addresses collected by your application before they reach your database, CRM, or mailing list.
Why verify before the send
Applications that collect email addresses through forms, signups, or integrations often receive invalid, disposable, or fake entries that degrade data quality and cause downstream deliverability problems. BillionVerify lets you intercept those addresses at the API layer — before they're stored or acted upon — so your pipelines process only clean, reachable contacts.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before 1shot API sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in 1shot API + BillionVerify",
"nodes": [
{
"parameters": {},
"type": "n8n-nodes-base.manualTrigger",
"typeVersion": 1,
"position": [
240,
300
],
"name": "When clicking ‘Test workflow’"
},
{
"parameters": {
"assignments": {
"assignments": [
{
"id": "email-field",
"name": "email",
"value": "jane@example.com",
"type": "string"
}
]
},
"options": {}
},
"type": "n8n-nodes-base.set",
"typeVersion": 3.4,
"position": [
460,
300
],
"name": "Get contacts"
},
{
"parameters": {
"sendTo": "={{ $json.email }}",
"subject": "Message for 1shot API contacts",
"message": "Replace this Gmail send with your 1shot API node — only deliverable, verified contacts reach it.",
"options": {}
},
"type": "n8n-nodes-base.gmail",
"typeVersion": 2.1,
"position": [
900,
300
],
"name": "Send email",
"webhookId": "",
"credentials": {
"gmailOAuth2": {
"id": "",
"name": "Gmail account"
}
}
},
{
"parameters": {
"operation": "verify",
"email": "={{ $json.email }}",
"additionalOptions": {}
},
"type": "n8n-nodes-billionverify.billionVerify",
"typeVersion": 1,
"position": [
540,
300
],
"name": "Verify Email (BillionVerify)",
"credentials": {
"billionVerifyApi": {
"id": "",
"name": "BillionVerify account"
}
}
},
{
"parameters": {
"conditions": {
"options": {
"caseSensitive": true,
"leftValue": "",
"typeValidation": "loose"
},
"combinator": "and",
"conditions": [
{
"id": "is-deliverable",
"leftValue": "={{ $json.is_deliverable }}",
"rightValue": "",
"operator": {
"type": "boolean",
"operation": "true",
"singleValue": true
}
}
]
}
},
"type": "n8n-nodes-base.if",
"typeVersion": 2,
"position": [
720,
300
],
"name": "IF deliverable"
}
],
"connections": {
"When clicking ‘Test workflow’": {
"main": [
[
{
"node": "Get contacts",
"type": "main",
"index": 0
}
]
]
},
"Get contacts": {
"main": [
[
{
"node": "Verify Email (BillionVerify)",
"type": "main",
"index": 0
}
]
]
},
"Verify Email (BillionVerify)": {
"main": [
[
{
"node": "IF deliverable",
"type": "main",
"index": 0
}
]
]
},
"IF deliverable": {
"main": [
[
{
"node": "Send email",
"type": "main",
"index": 0
}
],
[]
]
}
},
"settings": {
"executionOrder": "v1"
}
}Workflow templates with 1shot API
Ready-to-use workflows that verify emails before 1shot API sends.
How it works
- 1
Add a BillionVerify REST API call as a step in your 1shot API workflow, passing the email address as a parameter.
- 2
BillionVerify evaluates the address for validity, disposability, role-based characteristics, and catch-all status.
- 3
Parse the JSON response to extract the verification verdict and risk signals.
- 4
Use conditional logic in your workflow to branch: proceed for valid addresses, skip or flag invalid and disposable ones.
- 5
Log results alongside the original request data for auditing and data-quality reporting.
When to use this
Validate addresses in API pipelines before storage
Chain a BillionVerify API call inside your 1shot API workflow to verify each incoming email before it's written to a database or forwarded to a third-party service. Invalid and disposable addresses are caught at the pipeline level, not after the damage is done.
Gate downstream actions on verification results
Use BillionVerify's response verdict as a conditional within your 1shot API flow. Only trigger CRM creation, welcome email sends, or webhook callbacks when an address passes verification — role-based and catch-all addresses can be routed to a review queue.
Bulk verify address lists via scripted API calls
For developers processing batches of collected addresses, 1shot API can loop over a list and call BillionVerify's bulk endpoint, collecting results for downstream filtering without building a dedicated service.
FAQ
Do I need the n8n node or Integrately to use BillionVerify with 1shot API?
No. Since 1shot API is designed for direct HTTP interactions, you can call BillionVerify's REST API endpoint natively without any additional integration layer. Authentication uses a standard API key.
What does BillionVerify return for a catch-all domain?
It returns a catch-all status indicating the domain accepts all incoming mail without confirming specific mailboxes. Your workflow can treat this as uncertain and apply custom risk logic rather than a hard block.
Can I verify emails in real time and in bulk with the same API?
Yes. BillionVerify supports both single-address real-time lookups and bulk submission endpoints, so you can use the same API key and base URL for both use cases within your 1shot API workflows.
How do I handle rate limits when processing large batches?
Use BillionVerify's bulk endpoint to submit lists in a single request rather than looping single-address calls. This is far more efficient and avoids hitting per-request rate limits for high-volume developer pipelines.
Verify emails in 1shot API
Create a free account, grab your API key, and stop bounces before they happen.
Get started free