Overview
Every HTTP request that NLPearl.AI sends to your systems comes from a fixed set of public IP addresses. If your server is behind a firewall, a WAF, a cloud security group, or any policy that only accepts known sources, add these addresses to its allowlist so the requests reach your endpoint.IP Addresses to Allow
NLPearl.AI outbound IP addresses
Where It Applies
These addresses cover every request NLPearl.AI sends to a URL you configured:Webhooks
Call, Lead, and Chat webhooks, for both Inbound and Outbound Pearls.
API Node
Pre-Call, In-Call, and Post-Call API requests, plus the requests sent from the Test API panel.
Credentials
Token requests made for a Refresh Token credential, sent to your Access Token URL.
Generic Text Channel
Pearl replies and conversation events sent to your Outbound URL.
This page covers the HTTP requests NLPearl.AI sends to you. To receive calls from your own SIP infrastructure, the SIP trunk has its own IP settings: see Custom VoIP.
Setting Up the Allowlist
1
Find where incoming traffic is filtered
Identify the component that filters the traffic reaching your endpoint: a firewall, a reverse proxy, a WAF, or a cloud security group (AWS, Azure, GCP…).
2
Add the NLPearl.AI addresses
Create an allow rule for each address listed above, on the port your endpoint listens on (usually
443 for HTTPS).3
Test the connection
Send a test request to your endpoint from the platform, for example with the Test API panel of an API node, and check that your server receives it.
If the request reaches your server, the allowlist is set up correctly.
Webhooks
Learn how to configure webhooks and authenticate their requests.
Account Security Settings
Manage session timeout, two-factor authentication, and audit logs.

