Dengage API Static IPs

QuotaGuard gives customer-controlled Dengage REST API requests two fixed public IPv4 sources for Dengage's default-blocked API IP Restriction.

Add both subscription addresses under Settings, Identity & Access Management, API IP Restriction. Dengage accepts individual addresses or ranges and grants REST API access only to trusted entries.

The network rule works alongside Dengage's generated API credentials, authenticated session, token expiration, and API User permissions. See Dengage's API IP Restriction documentation.

Two stable QuotaGuard source nodes connected to a Dengage REST API destination

Satisfy Dengage's Default-Blocked API IP Restriction

Dengage says API Users are blocked by default from reaching its REST APIs from internet addresses. The API IP Restriction list defines the specific sources or ranges that are trusted to use API functions.

QuotaGuard turns a changing cloud source into two stable entries without changing the Dengage endpoint or weakening its separate authentication controls.

Configure the Restriction in Identity & Access Management

Open Settings, Identity & Access Management, then API IP Restriction. Dengage lets the operator name each definition so the two QuotaGuard sources can be identified as part of the same application route.

Add Both Addresses as Trusted Sources

Select the single-IP option for each public IPv4 address shown on the relevant QuotaGuard subscription. Dengage says the number of definitions is limited but does not publish a numerical limit on the current page, so remove obsolete entries deliberately.

Block Requests That Bypass the Pair

Dengage grants API access only to trusted source definitions. A request that leaves directly through an unregistered cloud address therefore fails the network gate before valid API credentials can make it eligible to use an API function.

Cloud API traffic routed through two QuotaGuard sources into Dengage API IP Restriction

Keep Network Trust Separate From API User Access

QuotaGuard supplies stable source identity. Dengage continues to authenticate the API User, establish the client session, apply permissions, and expire the access token.

This layered design lets teams stabilize network access without turning an IP address into a password or expanding what an automation can do.

Retain the Generated API Credentials

Dengage generates the API User name and password when an administrator creates the user. The password is displayed once and sent to the registered email address, so the client still needs appropriate credential storage after its source is trusted.

Preserve Read and Manage Permissions

API User permissions remain specific to documented areas such as transactional messaging, Data Space, content, sends, and reports. Dengage distinguishes Read from Manage and includes Read when Manage is granted.

Renew the Authenticated Session

The client authenticates before calling other REST API operations. Dengage documents a standard access-token lifetime of 3,600 seconds and notes that an account may use a custom expiration, so a stable source does not remove token-renewal handling.

Separate trusted-source, API User, session-token, and permission controls for Dengage REST API traffic

Change Trusted Sources Without Stranding API Clients

Dengage says saved IP-restriction changes become effective automatically within five minutes. A controlled overlap keeps the existing route available while both QuotaGuard sources are added and verified.

The restriction discussed here governs REST API traffic only. Keep separate Dengage access paths and opposite-direction traffic out of this network rule.

Confirm the Observed QuotaGuard Source

Route the same customer-controlled HTTP or HTTPS client through QuotaGuard and confirm that the observed egress address matches one of the subscription's two dashboard IPs. Keep both addresses registered because load balancing and failover may select either source.

Allow for the Five-Minute Activation Window

Add both QuotaGuard definitions before removing an existing trusted source. Wait for Dengage's documented activation window, verify a harmless REST API operation through the new route, and remove the old definition only after the intended path works.

Keep FTP and Outbound Traffic Separate

Dengage documents FTP IP restrictions as a separate setting, so this REST API rule should not be presented as governing FTP connections. Dengage messages, callbacks, or other traffic leaving its platform also travel in the opposite direction and need their own controls.

Five-minute Dengage REST API source cutover with a separate FTP IP Restriction lane

FAQs

Common questions about Dengage API static IPs and QuotaGuard.

Does the Dengage REST API require a static IP?

Dengage's current documentation says REST API access is blocked by default for API Users from any internet IP address. The operator must define trusted source IP addresses or ranges before those API Users can access API functions. A stable source is therefore required when the client runs on infrastructure whose native outbound address changes.

Where do I configure Dengage API IP Restriction?

Open Settings, Identity & Access Management, then API IP Restriction. The page lists existing definitions and lets you add, edit, or delete trusted sources. Give each definition a recognizable name so the two entries can be traced to the correct QuotaGuard subscription.

Which QuotaGuard addresses should I add to Dengage?

Add both individual public IPv4 addresses shown for the relevant QuotaGuard subscription. Choose Dengage's single-IP option for each address rather than entering the proxy hostname or assuming one source will always be used. Both entries must remain trusted because QuotaGuard load balances and fails over across the pair.

Does Dengage accept CIDR entries?

The current Dengage page documents a single IP option and an explicit IP-range option. It does not describe CIDR notation on that page, so enter each QuotaGuard IPv4 address as its own single-IP definition. Dengage also says the number of definitions is limited without publishing a numerical limit there.

How quickly does a Dengage IP change take effect?

Dengage says saved IP restrictions become effective automatically within five minutes. During a migration, retain the existing trusted source while adding both QuotaGuard addresses, wait for that window, and verify the REST API route before deleting the old entry. That overlap avoids making the cutover depend on an instantaneous settings update.

Does QuotaGuard replace Dengage API authentication?

No. Dengage still authenticates the generated API User name and password, establishes the client session, applies its Read or Manage permissions, and enforces token expiration. Dengage documents a standard access-token lifetime of 3,600 seconds, although an account may have a custom expiration.

How long does the QuotaGuard side of setup take?

The network work consists of routing the customer-controlled HTTP or HTTPS client through QuotaGuard and adding both observed dashboard addresses to Dengage. Actual setup time depends on whether that client supports an authenticated proxy and whether the operator can edit Identity & Access Management settings. Dengage's separate settings activation may then take up to five minutes.

Should I use QuotaGuard Static or Shield for the Dengage API?

Use Static for ordinary non-regulated HTTPS API traffic when a standard authenticated proxy meets the customer's policy. Use Shield when the customer-to-proxy hop must also be TLS-encrypted or the workflow carries regulated data. With either product, the application-to-Dengage HTTPS session remains encrypted and QuotaGuard does not decrypt its payload.

Can I get dedicated IPs for the Dengage API?

Yes. Dedicated IPs and proxy resources are included on direct Enterprise plans, currently $219 per month for QuotaGuard Static and $269 per month for QuotaGuard Shield. Starter, Production, and Business use shared static IP pairs, but each subscription still receives its own two-address pair to enter in Dengage.

Does this integration cover Dengage FTP or outbound messages?

No. This page covers REST API requests traveling from the customer's application through QuotaGuard to Dengage. Dengage documents FTP IP restriction separately, while messages, callbacks, or other traffic leaving Dengage travel in the opposite direction and require their own access-control design.

🚀 Ready to Get Started? Choose Your QuotaGuard Path

QuotaGuard STATIC

Why: You need a rock-solid, fixed IP for general API access, AI workflows, or standard third-party integrations.
Best For: Developers, startups, and general application connectivity.
Key Feature: SOCKS5 support for secure database access.
Sign Up for QG Static

QuotaGuard SHIELD

Why: You handle PHI, payment card data, or sensitive PII and require TLS encryption on the customer-to-proxy hop while preserving your application’s HTTPS session to its destination.
Best For: Regulated industries, financial services, and healthcare.
Key Feature: TLS-encrypted proxy connection with the destination HTTPS session preserved.
Sign Up for QG Shield

Trusted by Engineering Teams Everywhere

What our customers say

Customer experiences, in their own words. Swipe or scroll to read more.

We've been using QuotaGuard Static for nearly six years to provide static IP addresses to our clients so they are able to whitelist our network traffic.

Read full testimonial

We've been using QuotaGuard Static for nearly six years to provide static IP addresses to our clients so they are able to whitelist our network traffic.

The service has been hassle free, has never "not worked" or had any downtime to my knowledge. The only time we've reached out to support was during a migration from one cloud provider to another to ensure that we wouldn't cause interruptions in the service ourselves. The service we received at that time was prompt and professional.

Zach ColonVP of Engineering at ItsaCheckmate.comSubmitted Oct 20, 2023

The app's backend runs on serverless functions, and the railway data provider I was using only accepted requests from a fixed IP address. QuotaGuard gave me exactly that, and my passengers' PNR status checks kept working.

Read full testimonial

I used QuotaGuard Static IPs for ClearBerth, my train app for Indian Railways passengers. The app's backend runs on serverless functions, and the railway data provider I was using only accepted requests from a fixed IP address. QuotaGuard gave me exactly that, and my passengers' PNR status checks kept working.

It helped me because I could keep building the app without worrying about how to get a static IP. For a solo developer that is a real relief.

The best thing about QuotaGuard is the owner himself. Michael is kind, thoughtful and genuinely warm. When I wrote to say thank you, he replied personally, said it made his Sunday morning, and offered a returning customer discount for any future project. You do not often get that from a service company. I would happily use QuotaGuard again and I recommend it to any developer who needs a static IP.

Aditya Bhattacharya, ClearBerth

Aditya BhattacharyaFounder of ClearBerth appSubmitted Oct 18, 2026

QuotaGuard provided a static IP address via a SOCKS5 proxy. Setting up the proxy and using it from my server was very straightforward.

Read full testimonial

I have a web app running in Heroku, and that server occasionally needs to FTP files from another host. That host required requests to come from a whitelisted IP address. QuotaGuard provided a static IP address via a SOCKS5 proxy. Setting up the proxy and using it from my server was very straightforward.

Stephen BeitzelCTO, Narrative TechnologiesSubmitted Mar 28, 2024

I use QuotaGuard to connect with various APIs that require IP whitelisting and run web automations that require a country-specific IP. The stability and reliability of the service have been nothing short of exceptional.

Read full testimonial

I use QuotaGuard to connect with various APIs that require IP whitelisting and run web automations that require a country-specific IP. The stability and reliability of the service have been nothing short of exceptional. It simply works as expected and whenever I’ve had any questions Michael and the team are always very quick to respond to emails. I would recommend them without a doubt.

Jose VilchesCEO at SIM StoreSubmitted Oct 29, 2023

QuotaGuard has been a reliable partner for us for many years. Their service has consistently been solid, and when we ran into a more unusual use case, their team understood the situation quickly and worked closely with us to resolve the issues.

Read full testimonial

QuotaGuard has been a reliable partner for us for many years. Their service has consistently been solid, and when we ran into a more unusual use case, their team understood the situation quickly and worked closely with us to resolve the issues. That level of responsiveness and support has made a real difference for us.

Anton Litvinenkoco-founder @ Import2Submitted Aug 11, 2026

QG helped us prove our pipeline and workflow with users and in the end, we would have stayed but we use AWS for all our production so we had to switch. Sorry to go but loved every minute of it!

Read full testimonial

QUOTAGUARD FTW! We used qg for spooling up a prototype that needed access to MongoDB through Heroku without having to use 0.0.0.0 in mdb whitelist. Big nono for privacy and security. QG helped as we were able to add it as a resource in Heroku and test our prototype. As the platform matured, more test users came on board and our bandwidth scaled to a point where we were no longer a prototype so we moved over to AWS which is where our production apps live. The team at QG is beyond awesome. I sent an email and I think within 24hrs or less we had solved the issues with Tim and Michael. The fact they didn't pester after signup was refreshing as well. They are Dev dev's who get it. QG helped us prove our pipeline and workflow with users and in the end, we would have stayed but we use AWS for all our production so we had to switch. Sorry to go but loved every minute of it!

Greg LuttonCEO Exsurgo TechnologiesSubmitted Jun 1, 2026

Even though the issue was bank related, Michael and Randall provided exceptional support and helped me troubleshoot the issue.

Read full testimonial

I've had a issue tunneling requests to my bank's VPOS through QuotaGuard.

Even though the issue was bank related, Michael and Randall provided exceptional support and helped me troubleshoot the issue.

5 stars service, highly recommended!

Ozgur S.FounderSubmitted Jul 21, 2026

The product works great - but where they really shine is the exceptional customer service.

Read full testimonial

I needed to configure a static IP address for my app running on Heroku, so I could connect to an external database in a more secure manner. A colleague recommended Quotaguard as an option.

The product works great - but where they really shine is the exceptional customer service. One of my background workers was sneakily polling, which didnt show on the logs, and the Quotaguard support team showed patience and knowledge helping me get to the root of the problem. Fantastic team.

AlexSubmitted Aug 1, 2024

QuotaGuard is an excellent company to work with, they really helped me out on my API issue. Appreciate them as a partner.

Read full testimonial

QuotaGuard is an excellent company to work with, they really helped me out on my API issue. Appreciate them as a partner.

John William MeyerCEO, Jump FinanceSubmitted Sep 30, 2026

Solid service. :) Does what's on the tin.

Read full testimonial

Solid service. :) Does what's on the tin. They know what they're doing, and I mean that in two ways: (1) their execution of their value offering is *solid*, and (2) they appear undistracted by things that *aren't* what they're doing. A "small, sharp tools", you know?

IsaacLightwardSubmitted Jan 25, 2024

Reliability Engineered for the Modern Cloud

For over a decade, QuotaGuard has provided reliable, high-performance static IP and proxy solutions for cloud environments like Heroku, Kubernetes, and AWS.

Get the fixed identity and security your application needs today.