API Usage & Rate Limiting Policy

API Usage & Rate Limiting Policy

To ensure high availability, peak performance, and a seamless experience for all users, eShipz implements a standardized API Rate Limiting Policy. These limits protect our infrastructure from surges and ensure that critical logistics data remains accessible and reliable.

Effective: 20th Jan 2026

1. Standard Rate Limits

The following limits apply account-wide across all eShipz API endpoints, including Create Shipment, Get Shipment, and Tracking Fetch:

  • Threshold: 300 API requests per minute.

  • Scope: Applied per IP address.

  • Monitoring: High-traffic endpoints are monitored in real-time. Automated throttling is triggered immediately upon exceeding these thresholds to protect system resources.

2. Optimization Strategy: Batch Processing

To maintain efficiency and stay within limits, we strongly recommend Batch Processing. This practice aligns with industry standards for high-volume logistics APIs.

  • Capacity: You can group up to 50 AWBs per single API call using the Get Shipment or Tracking Fetch endpoints.

  • Performance: Utilizing batch parameters can reduce latency by up to 90% compared to sequential individual requests.

  • Best Practice: Avoid single AWB calls for bulk operations. Using batch parameters as documented in the API reference significantly reduces unnecessary server load.

3. Error Handling (HTTP 429)

If your application exceeds the 300-call-per-minute limit, the server will return an HTTP 429 "Too Many Requests" status code.

Sample JSON Response:

JSON
{
  "error": "rate_limit_exceeded",
  "message": "Too many requests. Please optimize calls (e.g., batch 50 AWBs) and retry after 60 seconds."
}

Recommended Recovery Steps:

  • Retry-After Header: Always check the Retry-After header in the response to determine the mandatory wait time before the next request.

  • Exponential Backoff: Implement an exponential backoff algorithm in your client-side code to manage retries gracefully and avoid immediate re-throttling.

4. Compliance & Stability

Adherence to these limits is essential for maintaining your account's health.
  1. Proactive Measure: Customers with exceptionally heavy workloads should implement internal safeguards to prevent automated IP blocking. Continuous non-compliance may lead to temporary IP blacklisting to ensure the stability of the broader eShipz ecosystem.


    • Related Articles

    • How to generate the FedEx web services API-Keys?

      Step 1 : Kindly visit http://www.fedex.com/in/newcustomer/and click on Get a Login to generate a login Id and password (if you have the login use the same) Step 2 : click on sign up/Login in on the top right. Step 3 : Login to your account. Step 4 : ...

    • eShipz Release Notes Jan 2024

      What’s new? Bluedart Migration Delete sales channel store Bluedart Migration BLUEDART has migrated its shippingApi from Soap to rest and to comply with it, eShipz also now provides a way to use BD's Rest API's. The below API’s have been migrated ...

    • Why are my orders not syncing from my store?

      Check Integration Status: First, verify that your sales channel integration (e.g., Shopify, Magento, WooCommerce) is active and properly authenticated. Go to Settings > Integrations to check the status. If you've recently changed your store's ...

    • Steps to integrate shiprocket B2C carrier

      Step 1: Login to Shiprocket. Step 2: Navigate to API settings (Settings → API → Add New API User) Step 3: Click on Create API user. In the pop-up form: Email address: enter unique email address. (Note: This must be different from the one used for ...

    • Release Notes -April Build 2025

      What’s New? Order Tag Filter Multi-select option for order tags Bug fix Order Tag The provision is provided where the user can see the order tag filter on ‘My Orders page. Click on ‘Filters’ [Refer Image No:1] Image No: 1 The user can now filter the ...