How do I disconnect or revoke the Mailjet integration?

Last updated May 20, 2026Integrations

Removing the Mailjet integration from Valid Email Checker is a two-step process for full hygiene. Step one: delete the connection on our side. Step two: revoke or regenerate the API Key and Secret Key pair inside Mailjet. Step one stops VEC from accessing Mailjet; step two ensures neither value can be reused.

Step 1: delete the connection in VEC

Sign into VEC and open Integrations.
Find the Mailjet row in Connected Integrations.
Click the three-dot row menu and pick Delete.
Confirm in the modal.
The Mailjet entry disappears from the table immediately.

Deleting the connection also clears the sync history attached to it. Past verification jobs remain in your Uploads & Results page as independent records.

Step 2: revoke the key pair in Mailjet

Sign into Mailjet.
Open Account Settings → REST API → API Keys.
Find the API Key and Secret Key pair you used to connect to Valid Email Checker.
Either delete the key pair or regenerate the Secret Key. Mailjet invalidates the old values immediately.

Both keys or just the secret?

Regenerating just the Secret Key invalidates the connection, since both values are required for authentication. Regenerating the API Key as well is more thorough. If the key pair is shared with other tools, regenerate carefully — every consumer of the old keys breaks.

What happens to running verifications?

A verification mid-import keeps running with the cached credentials. New sync attempts fail immediately until you reconnect.

Reconnecting later

Go to Integrations → Connect Integration → Mailjet and paste fresh API Key + Secret Key values. The new connection is unrelated to the deleted one. If you previously named it something distinctive (recommended in multi-account workflows), reuse the name for team-facing consistency.

Impact on transactional sending

Disconnecting the Mailjet integration only removes VEC access to your Contact Lists. Transactional sending, domain configuration, and SMTP credentials are independent. Your application code that uses Mailjet for transactional email continues to work — assuming it uses its own dedicated key pair. If the same pair was used for both, regenerating requires updating your application configuration.

Team-member-created connections

Connections created by team members show a Users badge in the Provider column. Owners can delete any connection; team members can only delete connections they themselves created.