Open Compliance in the Requesty Console and select Set up (or Edit) next to Allowed IPs.
Allowed IPs is in beta. It controls traffic to Requesty. For the addresses Requesty uses to reach your systems, see Static Egress IPs.
Who can use it
Only organization admins can view and change the list. See RBAC for the full role breakdown.Set up an allowlist
1
Find your public addresses
Collect the public IPv4 addresses your traffic leaves from. For traffic behind a VPN, proxy, or NAT gateway, that is the egress address of that network, not the private address of the machine.
2
Open the Allowed IPs editor
On the Compliance page, select Set up next to Allowed IPs.
3
Add your addresses
Choose Restricted and add each address or range. Each entry is a single IPv4 address, such as
203.0.113.5, or a CIDR range, such as 203.0.113.0/24 for 203.0.113.0 to 203.0.113.255.4
Save and test
Save the list, then send a test request from an allowed network and one from outside it to confirm the result.
Address rules
- IPv4 only. IPv6 addresses are not supported, and requests that arrive over IPv6 are rejected while a list is set.
- A range must start on its network boundary:
203.0.113.0/24is valid,203.0.113.5/24is not. - Duplicate entries are removed and the list is stored in sorted order.
What it covers
The list applies to the whole organization. It cannot yet be set per API key, group, or project.
Rejected requests
A request from an address outside the list fails before it reaches a model provider, so it is not billed. It returns403 with this message: