Verify Before Report
A 2-step recipe with EmailRep. We can help you get access.
Recipe · 2 steps
Verify Before Report
with EmailRep
Verify the address resolves, then branch into reporting it or ending cleanly.
- Query the address to confirm its domain exists and capture the deliverability signals before deciding whether to report it.
- File the malicious-behavior report for the verified address, recording the supplied tags, description, observation timestamp, and risk window.
What you'll need to have ready
- apiKey: EmailRep API key passed in the Key header on every request.
- email: The email address to verify and conditionally report.
- tags: Tags classifying the malicious behavior recorded with the report.
- description: Optional human-readable context recorded with the report.
- timestamp: Unix epoch seconds when the malicious activity was observed.
- expires: Number of hours the reported address should be treated as risky.
For your developer
Arazzo workflow emailrep:verify-before-report, 2 operations: queryEmailReputation → reportEmail. Specs on APIs.io.