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

    • Data Retention Policy

      1. Purpose This Data Retention Policy outlines how eShipz retains and manages customer data on its platform. The policy is designed to enhance data security, ensure regulatory compliance, and maintain platform performance. 2. Scope This policy ...

    • 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 : ...

    • Blue Dart API Key Error – Shipping or Tracking License Key Invalid/Expired

      If you encounter an error while creating shipments or tracking Blue Dart shipments in eShipz, it may be due to an expired or invalid Shipping License Key or Tracking License Key configured for your Blue Dart account. This article explains the cause ...

    • Credit Allocation in eShipz in New UI

      1. What are the available options for credits allocation? You can choose from the following options based on your requirement to allocate credits to the child user: Allocate Specific Credits Use Your Account Credits 2. What does “Allocate Specific ...

    • Steps to integrate shiprocket B2C carrier

      This article offers a step-by-step walkthrough to help you with the carrier configuration process of Shiprocket (B2C) carrier. This is B2C carrier. Step 1: Login to Shiprocket. Step 2: Navigate to API settings (Settings → API → Add New API User) Step ...