Static outbound IPs for the SendGrid API

Give your application’s SendGrid API requests a predictable source IP. QuotaGuard routes the requests through a static IP pair that you can add to SendGrid IP Access Management, so your cloud application can use an approved outbound path as it deploys and scales.

Primary action: View QuotaGuard Static plans

Secondary action: Explore the setup documentation

Keep your SendGrid allowlist manageable

A changing application IP creates extra work when access depends on an allowlist. You need to identify the new address, update the destination, and check that every worker is still using the approved path.

QuotaGuard gives that workflow a stable network boundary. Configure the HTTP client that calls SendGrid to use your QuotaGuard proxy connection, then register both assigned addresses with SendGrid. You can keep unrelated application traffic on its existing route.

This is useful for transactional email workers, server-side applications, scheduled jobs, and custom automations that can configure their outbound HTTP connections.

How the connection works

Your application
  -> QuotaGuard static outbound IPs
  -> SendGrid HTTPS API
  -> SendGrid email delivery
  -> Recipient

The QuotaGuard addresses identify the application-to-SendGrid connection. Your sender authentication, templates, recipients, and SendGrid delivery configuration remain part of your existing email setup.

SendGrid’s dedicated sending IPs govern the separate email-delivery connection. QuotaGuard does not replace a SendGrid sending IP, warm it up, or provide an inbox-placement guarantee. How SendGrid dedicated IPs work

Configure the requests you want to route

Store the QuotaGuard proxy connection in your runtime’s secret configuration. Then configure the actual client or worker that opens the SendGrid request.

A dedicated SendGrid HTTP client keeps the scope clear. It can use the QuotaGuard route while your payment client, database driver, and other network clients continue using their current connections. An environment variable is a configuration value, not a network-wide routing rule.

For SDK-based applications, use the SDK’s supported transport configuration for your installed version. If the runtime does not expose outbound proxy configuration, review the available architecture before selecting an approach.

A setup sequence that protects account access

1. Identify every process that uses the SendGrid account, including workers and SMTP clients.
2. Preserve an approved administrator browser path before enabling IP restrictions.
3. Store the proxy connection and record both assigned QuotaGuard addresses.
4. Verify the outbound IP from the deployed sending runtime.
5. Add both assigned IPs without removing other necessary approved entries.
6. Validate a complete Mail Send request in SendGrid sandbox mode, then perform a separately approved live check.

SendGrid enables IP Access Management when you add the first allowed address, and the restriction covers its UI, API, and SMTP relay. Your browser does not inherit your application’s proxy settings. SendGrid access management documentation

Match the plan to your network requirements

Choose capacity based on your API traffic and bandwidth. If your policy needs an IP pair reserved for your account, choose dedicated IPs rather than a shared static pair.

QuotaGuard Static Starter, Production, and Business use shared static IP pairs. Static Enterprise includes dedicated IPs and proxy resources. See current plans and pricing for the available capacity and support options.

Common questions

Will this change the IP that recipient mail servers see?

The QuotaGuard proxy changes the source IP used for the application-to-SendGrid API request. SendGrid continues to deliver the email using its own sending infrastructure.

Do I need to proxy every request from my application?

No. Configure the client that handles SendGrid. Keep other clients separate if their traffic should continue on its existing route.

Should I allow one or both QuotaGuard IPs?

Allow both addresses assigned in your dashboard. Seeing one address in a short verification check does not mean the other address is unnecessary.

Does a successful sandbox request send a test email?

No. SendGrid sandbox mode validates the request without delivery. Use a controlled live message, with an approved recipient, to check the delivery path. Sandbox mode behavior

Does this guide cover SMTP relay configuration?

The configuration here is for the HTTPS API. SMTP uses a different client and network path. Inventory existing SMTP clients before enabling SendGrid restrictions, and review their routing separately.

Set up a stable outbound path for SendGrid

Keep your email workflow and add an explicit route for the API requests that need an approved source IP.

Choose a QuotaGuard Static plan and follow the runtime documentation to configure the client that sends your email requests.

Guides and examples

• Quickstart
• Troubleshooting
• Ip addresses explained
• Downloadable examples and reference

Table of contents

• SendGrid example code and offline checks
• SendGrid sending IPs and application static IPs explained
• Troubleshoot SendGrid API access through QuotaGuard
• Use QuotaGuard Static with the SendGrid HTTPS API