Restriction & Limitation

Restriction

Non-SSL protocols such as HTTP, are not supported for security reasons.

To ensure data integrity and confidentiality, all webhook requests must be sent over a secure protocol like HTTPS. This guarantees that the communication between the API and the receiving endpoint is encrypted, protecting sensitive information from being intercepted or tampered with. It is strongly recommended to always use secure protocols to maintain the highest level of security when handling webhook events.

Limitation

Currently, each company can configure up to 10 webhooks.

Each webhook is limited to a single URL, with the ability to specify custom headers for each request sent. It is also possible to define the HTTP method to be used, such as POST, PATCH, or PUT, though the use of POST is recommended for compatibility and best practices.

This limit allows for optimized resource management while providing enough flexibility to cover a wide range of events related to shipments and their associated relationships.