Dengage API

QuotaGuard routes customer-controlled Dengage REST API requests through the two fixed public IPv4 addresses assigned to the subscription. Add both addresses as separate single-IP definitions under API IP Restriction so either healthy QuotaGuard route can satisfy the trusted-source rule. QuotaGuard has provided static-IP proxy service since 2013.

• Default-Blocked REST API Access: Dengage says API Users are blocked by default from accessing its REST APIs from internet addresses. Only IP addresses or ranges entered in API IP Restriction are trusted.
• Five-Minute Activation: Dengage says a saved IP-restriction change takes effect automatically within five minutes. Keep the existing definitions during a cutover until both QuotaGuard sources have been added and observed.
• API User Controls Preserved: Dengage still authenticates the generated API username and password, creates the client session, applies the API User's Read or Manage permissions, and enforces token expiration. QuotaGuard supplies network identity without replacing those controls.
• Multi-Platform Support: Use the same pair from Heroku, Render, Railway, Fly.io, AWS Lambda, Vercel, Netlify Functions, Kubernetes, or a direct VPS when the customer controls an HTTP or HTTPS client that supports an authenticated proxy.
• Production-Grade Reliability: Each subscription receives two load-balanced static IPv4 addresses with health checks and automated failover. Add both as separate Dengage IP definitions so either healthy source remains accepted.
• Shield for Regulated Data: The application-to-Dengage HTTPS session remains encrypted with either product. Shield additionally encrypts the customer-to-proxy hop and is the supported QuotaGuard product when the workflow carries regulated data.

REST API scope note: This integration covers requests from the customer's application to Dengage REST APIs. Dengage documents FTP IP restrictions separately, and outbound messages or callbacks travel in a different direction.