These API Terms apply when a business account uses the Topping Courier API, webhooks or integrations (such as our WooCommerce plugin). They add to our Terms of Service, which also apply to every delivery booked through the API.
1. Access and keys
1.1 API access is available to business accounts that we approve. We may set daily and monthly request limits, shown in your account.
1.2 API keys are like passwords. Keep them secret, store them securely, and never put them in a website, app or code that others can see. You are responsible for all requests made with your keys.
1.3 If a key may have been exposed, revoke it in your account right away and create a new one. We may revoke keys that are exposed or misused. We recommend rotating keys at least once a year.
2. Test and live keys
Test keys use the sandbox: test bookings are never dispatched or charged. Live keys create real deliveries that are charged under the Terms of Service.
3. Acceptable use
You agree not to:
- send requests faster than the limits allow, or try to get around them;
- book deliveries you don't intend to send, or use the API for price scraping;
- probe, attack or interfere with our systems;
- share access with anyone outside your business;
- send us personal information you aren't allowed to share.
4. Webhooks
Webhooks are sent to the HTTPS address you register. Each request is signed; check the signature before trusting it. We retry failed webhooks several times, then stop. Your endpoint should answer quickly and handle the same event more than once.
5. Your data and ours
You keep ownership of the information you send us. You allow us to use it to provide the service. Our API, documentation and data structures belong to Topping Courier Inc.
6. Changes and availability
We aim for the API to be available at all times but don't guarantee it. We may change the API; we will give at least 30 days' notice of changes that could break an existing integration, except for urgent security fixes.
7. Ending access
You can stop using the API at any time. We may suspend or end API access if you break these terms, don't pay, or create a security risk.
8. Liability
The API is provided "as is". Our liability for deliveries is set out in the Terms of Service. We are not liable for losses caused by problems with your own systems or integrations.