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.
We want to refer to the customer's username when packing the order. Right now, to do this, we need to download the tiktok orders, connect them to the shopify order number via the tiktok order in the notes field and then connect that to the order number in shipbob.
If we had the username in shopify, we could eliminate the step where we have to connect tiktok to shopify.
When exchanging a product, you have to pick from a list of products, sorted by the most recently created products. There's no search facility. This is particularly problematic when you have an old sku that comes in every season and it is buried deep in the list
I want to fully customize different free shipping thresholds for different currencies/regions.
This would better compensate for my shipping costs in different currencies and may also increase the order value.
A notification to give the customer the opportunity to change their requested ship date. This allows wineries to change the date without re-directing. Using the RSD and sending a notification 3 days or so before.
Would you be able to:
1. Add a functionality that restricts order views based on a ship from location or/or login? We have multiple ship from locations and we are 100% manula orders; it creates confusion when one warehouse sees orders from another warehouse.
2. Have a ship to address book and have that be varied based on ship from locations. We have set ship to locations and it doesnt change often.