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.
My idea is that when a shipment comes in from China to America,instead of each parcel going right to LAX through customs,each one should go to it's respective state and provence,every state has a sorting and customs center,it would just make it easier to make one stop instead of two or three on the way to the packages final point of delivery,
I hope to insert a form in the email, allowing customers to fill out the form directly within the email.
For example, if there are some events or new product launches, I would like to invite users to participate and collect information on whether they are interested or not.
Hi, I hope you can include a column where users can also see "WHEN" the order arrived in customs clearance and "WHEN" it was released. I am referring to ALL orders, not just the delayed orders.