Skip to content
← MailMaid Academy
Developers

Integrate verification without exposing a secret

Short answer

Put the provider call behind your own server and preserve failure states.

Create a narrow key#

Use a verification-only MailMaid API key. Store it in your server’s secret store, never a public browser bundle or query string. Give each integration a recognizable label so it can be revoked independently.

Handle the complete result#

Branch on status and reason. A timeout is not evidence that an address is invalid or deliverable. Decide whether an unknown result should pause a workflow, request confirmation or enter a review queue. Keep this policy explicit.

Bound cost and retries#

Test with addresses you control. Respect rate limits, keep request logs free of tokens and avoid retrying an ambiguous paid request automatically. Reviewed bulk jobs support a request ID to reduce duplicate work; retain it with the job record.

Keep reading

Sender reputation

A practical preflight before a large send

Review the audience, sending path and stop conditions together.

2 min read
Teams

A repeatable list hygiene workflow for agencies

Keep client identity, decisions and report ownership clear.

2 min read
List hygiene

A suppression list should survive every cleaning pass

A new verification result must not erase a recipient’s choice.

2 min read