Shipbubble API Documentation
  • Shipbubble API
  • Get started
    • Authentication
    • Request and Responses
    • Errors
    • Rate Limiting
    • Pagination
    • Postman
  • API Reference
    • Wallet
      • Get shipping wallet balance
      • Request wallet fund
    • Addresses
      • Validate address (global)
      • Get validated addresses
      • Edit address details
      • Get single address details
    • Package categories
    • Package dimensions
    • Couriers
    • Rates
      • Request shipping rates
      • Request shipping rates from selected couriers
      • Edit request token details
    • Cash on delivery
    • Insurance
      • Get Insurance Rates
    • Shipments
      • Create shipment
      • Cancel shipment
    • Returns
      • Get rates for a return shipment request
    • Tracking
      • Get shipments
      • Get multiple specific shipments
    • Webhooks
      • Webhook simulator (sandbox)
Powered by GitBook
On this page

Was this helpful?

  1. Get started

Errors

Shipbubble APIs uses conventional HTTP response codes to indicate the success or failure of an API request.

In general: Code “200” indicates success. Codes in the 4xx range indicate an error that failed given the information provided (e.g. a required parameter was omitted, invalid request body, etc.). Codes in the 5xx range indicate an error with Shipbubbles' servers (these are rare).

Below is a description of our error codes:

Response code
Description

400

Invalid request, account error (eg no kyc, insufficient wallet balance etc), description is usually included in message property

401

No valid API key provided

403

API key does not have permission to perform request

404

Requested resource is not found

422

Invalid data values sumbitted in the request body

429

Too many requests, rate limit reached

500

Our servers cannot process request at the moment (These are rare)

503

Third-party service unavailable (please contact us as soon as you see this error)

PreviousRequest and ResponsesNextRate Limiting

Last updated 2 years ago

Was this helpful?