Sendwithus has released a new version of the SendGrid integration which now supports the use of SendGrid API Keys as a form of authentication. We recommend moving over to the API Key system if you are currently using the older integration.
Previously, Sendwithus used your SendGrid credentials to authenticate when sending email through your SendGrid account. This connection method came with some limitations. For example, if a SendGrid’s account password was rotated then it would need to be manually updated in Sendwithus. With the use of SendGrid API keys in the upgraded SendGrid integration, you won’t have to worry about this issue.
How can I tell I’m using a previous version of SendGrid integration?
On your Delivery Settings page, SendGrid legacy accounts will be identified with a warning icon as shown in the picture below.
How do I switch over to use the new SendGrid integration?
You can use the new SendGrid integration by setting up a new ESP account. For more information, click here to learn how to connect a SendGrid account to Sendwithus.
Things to consider before removing a SendGrid Legacy Account
- Are any of your templates currently sending using Template Overrides?
- If yes, you will need to make sure you switch the template overrides to use the newly created ESP Account ID. Note: by removing an ESP account, all previously assigned template overrides will be moved to your “Default” ESP.
- Is any of your internal system’s code using the SendGrid Legacy ESP Account ID?
- If yes, you’ll have to search your code for the that ESP Account ID and replace it with the newly created ESP Account ID. IMPORTANT: If you remove the ESP account and continue to make API calls using the old ESP Account ID, the API response will be a 400 Bad Request, which results in the email not sending.
- Are you currently receiving webhooks from your SendGrid Legacy account?
- If your system is set up to receive webhooks, you must add the URL endpoint to the newly created ESP. The webhooks you receive will be in the same exact format as the previous integration. Click here to see what those webhooks look like.
- Are any of your SendGrid Legacy accounts SendGrid subusers?
- If you have multiple SendGrid accounts attached to Sendwithus as SendGrid subusers, you will need to use a different API key for each Subuser to connect them with Sendwithus. Each SendGrid Subuser will have its own API Key management section.
When do I need to move over to the new system?
Currently, we will continue to support both integrations but we highly recommend you switch over to use the new system. Expect an announcement when we plan on removing SendGrid Legacy support.
Will I need to do anything differently besides changing ESP Account ID’s
Nope! Everything will be done exactly the same. Since you’re now using an API key for that same SendGrid account, all Sendgrid settings will be the exact same. This includes suppression lists, email events, tracking settings, etc.
Do you have any additional questions? Reach out to the support team at firstname.lastname@example.org and we’d be happy to help.