Talk to our team

Documentation

✉️ Email Delivery

Documentation, reference material and tutorials for CRM-NG SMTP Email: setup guides for every mail service, troubleshooting, and one article per error message.

Error: ENDPOINT_PERMISSION_DENIED (SMTP2GO)

Updated

By Duane GarnerChief Executive Officer (CEO)
Summarize: Claude ChatGPT View Markdown
On this page

The SMTP2GO API key is valid but not allowed to use the email-sending endpoint. Give the key sending permission and test again.

Shown by the SMTP2GO mailer

The test result or the error log shows ENDPOINT_PERMISSION_DENIED when CRM-NG SMTP sends through SMTP2GO.

This article is for site owners using the SMTP2GO mailer whose test fails with this code.

What this error means

SMTP2GO API keys carry a list of the API endpoints they may use. Each endpoint is one kind of action, such as sending an email, reading statistics or managing senders. CRM-NG SMTP uses the email-send endpoint. When the key is not permitted to use that endpoint, SMTP2GO stops the request and answers with this code.

So the key is real and active. It just was not given the one permission CRM-NG SMTP needs.

Common causes

  • The key was created for another tool, such as a reporting dashboard, and only has read permissions.
  • Someone narrowed the key's permissions after it was saved in CRM-NG SMTP.
  • The key was created with a custom permission set and the email-sending endpoints were left unticked.
  • You copied a key from a different SMTP2GO account or sub-account than the one you meant to use.

How to fix

  1. Sign in to SMTP2GO

    Open https://app.smtp2go.com/ with the account that sends for this site.

  2. Open the API keys page

    Go to Sending → API Keys. Find the key used by this site and open it.

  3. Check its permissions

    In the key's settings, look at the permissions or endpoints list. Turn on the email-sending endpoints (the ones under the email section, including the plain send endpoint). Save the key.

  4. Or create a new key

    If you prefer a clean key, add a new API key, keep sending permission on and name it after the site. Copy it.

  5. Update CRM-NG SMTP if you made a new key

    Go to CRM-NG SMTP → Settings → General, check Mailer is SMTP2GO, press Remove API Key, paste the new key into API Key and save.

  6. Send a test

    Go to CRM-NG SMTP → Tools → Email Test, fill in Send To and press Send Email.

Verify it worked

The test page shows "Test email sent successfully! Check your inbox to confirm delivery." In SMTP2GO, the sent-email activity or reports page lists the test message.

Notes

  • Permission changes on an existing key usually apply straight away. If the error stays after saving, wait a minute and test again, then try a new key.
  • Your From address must also be a verified sender or on a verified sender domain in SMTP2GO. If the next error mentions the sender, verify it under the sender settings in SMTP2GO.
  • SMTP2GO keys can also be limited by IP. If you set that, include your web server's outbound IP.
Go to Top