SendGrid sending IPs and application static IPs explained
If you need a fixed IP for SendGrid, start with the connection you want to control. An application’s API requests and SendGrid’s email delivery use different network paths, with different IP addresses and different purposes.
Choosing the correct path helps you solve the access-control problem without changing an email delivery setup that already works.
The application connects to SendGrid
Your application submits an HTTPS request to SendGrid’s API. The source address on that request comes from the application’s outbound network path.
If SendGrid IP Access Management is enabled, that source address must be allowed. A stable application egress address makes the allowlist easier to manage when you deploy new application instances or run workers on infrastructure with changing default outbound addresses.
QuotaGuard operates on this side of the connection. A proxy-aware HTTP client can send its SendGrid requests through the QuotaGuard outbound proxy, so SendGrid receives them from one of the assigned QuotaGuard IPs.
SendGrid delivers the email
Once SendGrid accepts a normal Mail Send request, its email infrastructure handles delivery to the recipient’s mail server. SendGrid can use shared sending IPs or dedicated sending IPs, depending on your account and email program.
The sending IP is relevant to the email delivery relationship with mailbox providers. SendGrid documents dedicated sending IPs, reputation, and warmup as part of that workflow. SendGrid dedicated IP addresses
Changing the application’s outbound route does not allocate a new SendGrid sending IP or perform warmup. It also does not replace domain authentication, appropriate sending practices, or delivery monitoring.
Compare the roles
| Question | Application egress IP | SendGrid sending IP |
|---|---|---|
| Which connection uses it? | Application to SendGrid API | SendGrid to recipient mail server |
| What is the relevant goal? | Predictable source address for API access controls | Email sending infrastructure and reputation management |
| Where is it configured? | Application HTTP client and network path | SendGrid email delivery configuration |
| What does QuotaGuard provide? | Static outbound proxy addresses | No replacement for SendGrid’s sending IP |
| What validates the path? | Egress check and authenticated API request | Delivery information and email-program monitoring |
Static and dedicated describe different properties
A static IP is stable. A dedicated IP is reserved for a particular customer or use. An address can be static while shared with other customers.
For application egress, QuotaGuard Static Starter, Production, and Business use shared static IP pairs. Static Enterprise includes dedicated IPs and proxy resources. Select the allocation that meets your policy rather than assuming “static” means “exclusive.” QuotaGuard pricing
Even a dedicated egress address is only one part of access control. Continue protecting the SendGrid API key and restricting its permissions. A source-IP check does not replace API authentication.
Keep account administration on an approved route
IP restrictions can affect more than the application you are configuring. SendGrid IP Access Management covers UI, API, and SMTP access once activated. Preserve the administrator’s approved browser route and account for other legitimate clients before changing the list. SendGrid IP Access Management
Do not add only the application proxy addresses and assume every account user will still be able to sign in. A browser on an office network or VPN normally has its own source address.
Choose a service for API access or email delivery
For an API-access requirement, evaluate your existing fixed egress, a managed proxy, or another approved network design. Consider runtime control, operational work, traffic, region, and whether the IP allocation must be dedicated.
For an email-sending requirement, evaluate SendGrid’s sending options and the needs of your email program. The price of an application egress service is not a substitute for the price of a SendGrid email plan.
You may need both: an approved source address for API access and a separate sending configuration that meets your delivery requirements. Keeping the two decisions separate makes each easier to review and operate.
Explore QuotaGuard Static for the application-to-API connection, and use SendGrid’s dedicated IP documentation for the email-sending side.
Download the reference examples · Integration overview