Integrating Clay with Private VM: IP Whitelisting and Alternatives | Clay

Integrating Clay with Private VM: IP Whitelisting and Alternatives

Hello, team! 🙂 We’re trying to integrate Clay with our private virtual machine (VM) that only accepts traffic from whitelisted IP addresses. Since our VM doesn’t allow external traffic from unknown sources, we need to know:

What are the outbound IP addresses or CIDR ranges that Clay uses to make API requests to external services? Do these IPs change frequently?
Does Clay provide dedicated IP addresses or any dedicated infrastructure for outbound calls?

This information is crucial for us to securely whitelist Clay’s outbound traffic and complete our integration. Looking forward to your reply. Thanks in advance! P.S. I see from your previous responses that Clay may not have dedicated outbound IPs. In that case, what alternatives do you recommend for securely integrating Clay’s HTTP API if we need to route it through our VM, which only allows traffic from whitelisted IPs?

4 comments

Channeled
APP
·
·
Clay doesn't have exposed API endpoints or dedicated outbound IPs for direct querying. Instead, we offer alternatives for programmatic use: 1. Send input data to Clay via webhooks 2. Process data within Clay 3. Use our HTTP API integration to send output to other services For secure integration, you can wrap Clay in a third-party tool like Replit or Make to create an API proxy. What specific security requirements does your VM have for incoming traffic?
Source: Using Clay as an API | Documentation | Clay University
Sergey K.
·
·
Hello Clay Support Team! 🙂 Thank you for the clarification. Regarding the security requirements for our virtual machine (VM):
Our VM only accepts inbound traffic from explicitly whitelisted IP addresses.
The VM does not allow external traffic from arbitrary sources, even if secured with tokens or HTTPS.
To enable secure integration with Clay, we need a way to identify or control the outbound IPs of the service interacting with our VM, so we can whitelist them.
If Clay’s HTTP API cannot guarantee fixed outbound IPs, and given that our VM is locked down, could you advise on the best way to set up a reliable and secure API proxy? We’d appreciate detailed suggestions (for example, using a third-party tool like Replit, Make, or something else) and any available documentation or examples for setting this up. Looking forward to your recommendations!
Channeled
APP
·
·
For your VM's IP whitelist requirements, use a third-party tool like Replit or Make as an API proxy wrapper around Clay. Setup approach: 1. Deploy proxy on Replit/Make with static IP 2. Configure proxy to receive your API requests 3. Proxy triggers Clay via webhooks for input data 4. Clay processes and enriches data 5. Clay sends results back via HTTP API integration 6. Whitelist your proxy's static IP on your VM Important considerations: ** Clay's enrichment responses can take a minute or more ** Build logic to handle async processing delays * Clay doesn't have exposed API endpoints for direct querying Check this tutorial on API proxying with Clay for implementation details.
Source: Using Clay as an API | Documentation | Clay University
Bo (.
·
·
Hey Sergey I noticed you reopened this ticket. Is there anything we can do for you?
Feel free to keep this conversation going or create a new ticket.