Security

Make sure you use a staging environment when developing against the Shippit APIs. You can access Shippit’s staging environment at https://app.staging.shippit.com/api/3/.

Implement robust error handling in your code to catch and manage API errors effectively. For more information about troubleshooting common errors, see the troubleshooting section.

Shippit maintains a rate limit of 60 requests per rolling 60 seconds per API key. Keep within this rate to avoid getting temporarily blocked. If you need a higher rate limit either temporarily or on a permanent basis, talk to your Shippit account manager, or contact Shippit support.

Shippit updates the API from time to time. Stay informed about changes and update your integration accordingly. For release notes, see the release notes collection on the Shippit help centre. For the change log, see the change log on the Shippit developer centre. You can also sign up for regular communications from the Shippit team.

SOC2 compliance

Shippit is SOC2 Type 2 compliant. This means that we have implemented a range of processes and procedures designed to keep your data safe, and to ensure that we meet best software development practices. SOC2 compliance covers items like managing user access, vulnerability scanning, business continuity and disaster recovery plans, data encryption, and responsible disclosure. If you need further information about our SOC2 Type 2 compliance, or require letters or statements confirming our compliance, talk to your Shippit account manager, or contact Shippit support.