Make. Connect the useful bits.
Add a ParseAPI lookup to your scenario with the HTTP app. One connection, plenty of possibilities.
/email/hello@gmail.com{
"email": "hello@gmail.com",
"valid": true,
"disposable": false,
"domain_valid": true
}Save your connection.
Get a secret key from API keys.
Add the current HTTP module and choose Make a request. Set Authentication type to API key, then create a keychain named ParseAPI.
Paste your key into Key. Choose In the header for placement and X-API-Key for the parameter name. Save the credential.
Check your first email.
The saved credential supplies authentication. Set Parse response to Yes and, in Advanced settings, Return error if HTTP request fails to Yes.
https://api.parseapi.com/email/hello%40gmail.com- Method
GET- Header name
Parse-Version- Header value
2.0.0- Query and body
- Leave empty
Save and run the module once. 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.
Place HTTP after a trigger that supplies an email. Keep https://api.parseapi.com/email/ fixed and insert the mapped email inside encodeURL(...). Encode only the email value.
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: Make request setup.