Publish Webhook Outgoing IPs as a Machine-Readable Plain-Text Endpoint

Currently, AfterShip's webhook outgoing IP list is only available on an HTML documentation page (https://www.aftership.com/docs/tracking/webhook/webhook-outgoing-ips). This makes it impossible to automate IP allowlist management in infrastructure-as-code (IaC) workflows.

Problem:

Teams that use IP-based firewalls to secure their webhook endpoints must manually monitor the documentation page for any IP changes and update their firewall rules accordingly. If a change is missed, it can cause webhook delivery failures and broken integrations.

Request:

Please publish the webhook outgoing IP list as a dedicated plain-text endpoint — similar to how Cloudflare publishes theirs at https://www.cloudflare.com/ips-v4 — where each IP is returned on a separate line.

This would allow teams to:

• Fetch the IP list programmatically as part of their CI/CD or IaC pipelines
• Keep firewall allowlists automatically in sync without manual intervention
• Avoid service disruptions caused by missed IP changes

This is a standard practice among major API providers and would significantly improve the developer experience for customers who manage network security programmatically.