Zapier. Turn a lookup into action.
Check an email in your Zap, then pass the answer to the next step.
/email/hello@gmail.com{
"email": "hello@gmail.com",
"valid": true,
"disposable": false,
"domain_valid": true
}API by Zapier requires a paid Zapier plan and is currently in beta. See requirements.
Save your connection.
Get a secret key from API keys.
In Zapier Apps, add an API by Zapier connection. Choose Static Headers (API key) and add X-API-Key with your key as its value.
Name it ParseAPI, set Domain filter to api.parseapi.com, and save. Leave the optional Test URL empty.
Check your first email.
In a Zap with a trigger, add API by Zapier, choose API Request, and select the ParseAPI connection.
https://api.parseapi.com/email/hello%40gmail.com- Method
GET- Header name
Parse-Version- Header value
2.0.0- Query and body
- Leave empty
Click Continue, then Test step. Inspect the response before adding your next action.
Core checks use your monthly request allowance. They describe email format and domain signals, not mailbox existence. The starter leaves the separately metered deep=true mailbox check off. Explore Email.
Bring your own data.
Add Formatter by Zapier before the API Request. Choose Text, then URL Encode, and map your trigger's original email into Input. In the request URL, replace the sample email with the formatter's output.
Test with a sample from your trigger, then map fields such as email, domain_valid and disposable into the next step.
Check the encoded value
hello+sales@gmail.com should become hello%2Bsales%40gmail.com. Encoding keeps special characters inside the email input.
Errors, unknowns and the next lookup
For invalid_api_key, check the selected credential and its X-API-Key header. Inspect non-200 responses before passing data to another step. See the error reference.
valid checks the format. domain_valid checks mail routing. Keep null as unknown. Choose another endpoint from the API reference and keep the same credentials and version header.
More setup help: Zapier request setup.