API Terms of Use

1What Nexgo API Provides

Nexgo APIs may allow approved merchants and technology partners to programmatically access logistics functionality, including:

• Create shipments
• Cancel shipments
• Generate AWBs
• Generate shipping labels
• Generate manifests
• Check shipment status
• Track shipments
• Fetch courier information
• Check pincode serviceability
• Calculate shipping rates
• Manage NDR
• Manage RTO
• Create reverse shipments
• Access COD information
• Retrieve invoices
• Access reports
• Receive shipment updates through webhooks
• Other logistics functionality made available by Nexgo

The specific API features available to you depend on your account, subscription, integration and applicable Nexgo documentation.

2API Access

API access may be provided only after Nexgo approves your account or integration.

Nexgo may provide:

• API keys
• Client IDs
• Client secrets
• Access tokens
• Webhook credentials
• Sandbox credentials
• Production credentials

You must use API credentials only for the account and purpose for which they were issued.

Nexgo may refuse, suspend or revoke API access where necessary for security, compliance, operational or commercial reasons.

3Developer Account

You are responsible for maintaining accurate information associated with your developer or merchant account.

You must promptly update:

• Business information
• Contact information
• Technical contact
• Authorized users
• Integration information
• Other relevant account details

You must ensure that only authorized personnel have access to your Nexgo API credentials.

4API Credentials

API credentials are confidential.

You must:

• Store credentials securely
• Restrict access to authorized personnel
• Use appropriate encryption and security controls
• Rotate credentials where necessary
• Immediately report compromised credentials
• You must not:
• Publish API keys publicly
• Upload credentials to public GitHub repositories
• Include secrets in client-side applications where avoidable
• Share credentials with unauthorized third parties
• Sell or transfer API credentials

If you believe your credentials have been compromised, notify Nexgo immediately.

Nexgo may deactivate compromised credentials and issue replacement credentials.

5Sandbox and Production

Where provided, Nexgo may offer separate:

Sandbox Environment

Used for:

• Development
• Testing
• Integration
• Debugging

Sandbox data may not represent actual production performance or availability.

Production Environment

Used for live shipments and real customer transactions.

You are responsible for testing your integration before sending production requests.

6API Documentation

Nexgo may provide technical documentation describing:

• Endpoints
• Request methods
• Parameters
• Authentication
• Response formats
• Error codes
• Webhooks
• Rate limits
• Integration requirements

Nexgo may update its documentation from time to time.

You are responsible for using the latest version of the documentation.

7Permitted API Usage

You may use Nexgo APIs only to:

• Integrate your business systems with Nexgo
• Automate legitimate shipping operations
• Manage your own shipments
• Manage shipments for customers you are authorized to represent
• Access information available to your account
• Perform other activities expressly authorized by Nexgo

Your API usage must comply with all applicable laws and the Nexgo Terms of Service.

8Prohibited API Activities

You must not use Nexgo APIs to:

• Gain unauthorized access
• Access another user's data
• Circumvent security controls
• Probe or scan Nexgo systems
• Reverse engineer Nexgo APIs
• Extract data beyond your authorization
• Scrape Nexgo services
• Create fake shipments
• Manipulate tracking information
• Abuse COD services
• Circumvent billing
• Circumvent rate limits
• Perform denial-of-service attacks
• Introduce malware
• Upload malicious code
• Conduct fraudulent activity
• Resell API access without authorization
• Use the API for unlawful activities

9Rate Limits

Nexgo may impose API rate limits to maintain platform stability and security.

Rate limits may apply to:

• Requests per second
• Requests per minute
• Requests per hour
• Daily requests
• Specific API endpoints
• Account-level usage

Your application must handle rate-limit responses appropriately.

Nexgo may temporarily restrict or suspend API access where excessive traffic threatens platform performance.

10Fair Usage

API access must be used responsibly.

You must not generate unnecessary requests, including repeated requests that could reasonably be avoided through:

• Caching
• Webhooks
• Pagination
• Incremental synchronization
• Appropriate retry logic

Where Nexgo provides webhooks for shipment updates, you should use webhooks instead of repeatedly polling APIs where reasonably possible.

11Retry Policy

Your application should use reasonable retry mechanisms.

You should avoid repeatedly retrying failed requests without appropriate delays.

For temporary failures, you should use an appropriate exponential backoff strategy.

You should not repeatedly retry requests that have received a permanent error response.

12Idempotency

Where Nexgo provides idempotency functionality, you should use idempotency keys for operations where duplicate requests could result in duplicate transactions or shipments.

For example:

• Shipment creation
• Pickup requests
• Reverse shipment creation
• Other transaction-based operations

You are responsible for designing your integration to minimize accidental duplicate operations.

13Shipment Creation

When creating a Shipment through the API, you must provide accurate information.

This may include:

• Sender information
• Receiver information
• Address
• Pincode
• Product details
• Product value
• Weight
• Dimensions
• Payment mode
• COD amount
• Invoice information
• Other required fields

You must not submit false, misleading or fraudulent information.

14Customer Data

Your API integration may process personal information belonging to your customers.

This may include:

• Customer name
• Phone number
• Email address
• Delivery address
• Order information
• Shipment information

You must have the appropriate legal authority to provide such information to Nexgo.

You must process customer information in accordance with applicable privacy and data-protection laws.

15Data Security

You are responsible for maintaining appropriate security measures for information received through Nexgo APIs.

You should:

• Encrypt sensitive information where appropriate
• Secure API credentials
• Restrict employee access
• Maintain access logs
• Monitor suspicious activity
• Use secure HTTPS connections
• Remove unnecessary stored data
• Protect webhook endpoints

You must notify Nexgo promptly if you discover a security incident involving Nexgo data or credentials.

16Webhooks

Nexgo may provide webhook notifications for events such as:

• Shipment created
• Pickup scheduled
• Pickup completed
• In transit
• Out for delivery
• Delivered
• NDR
• RTO
• RTO delivered
• Shipment cancelled
• COD updates
• Other shipment events

Webhook events may be delivered more than once.

Your system should therefore be designed to safely handle duplicate events.

17Webhook Security

You are responsible for securing your webhook endpoints.

Where Nexgo provides webhook signatures or authentication mechanisms, you should verify them before processing webhook requests.

You should not expose webhook endpoints unnecessarily.

You should also protect your system against:

• Replay attacks
• Duplicate events
• Unauthorized requests
• Malformed payloads
• Excessive requests

18API Response Data

Information returned through the Nexgo API may be confidential or subject to restrictions.

You may use API response data only for legitimate purposes connected with your Nexgo account and authorized integration.

You must not:

• Sell Nexgo data
• Create unauthorized databases
• Publish private shipment information
• Share customer information without authorization
• Use data for unrelated purposes

19Data Retention

You should retain API data only for as long as reasonably necessary for your legitimate business purpose or as required by applicable law.

Where customer or personal information is no longer required, you should securely delete or anonymize it where appropriate.

Nexgo may maintain API logs and records for security, operational, accounting, legal and compliance purposes.

20Third-Party Integrations

You may integrate Nexgo with third-party systems such as:

• Ecommerce platforms
• Marketplaces
• ERP systems
• OMS systems
• WMS systems
• CRM systems
• Payment systems
• Other software

You are responsible for ensuring that your third-party integrations comply with applicable terms and privacy requirements.

Nexgo is not responsible for failures caused solely by third-party systems.

21API Changes

Nexgo may modify APIs from time to time.

Changes may include:

• New endpoints
• New fields
• New features
• Bug fixes
• Security improvements
• Performance improvements
• Deprecated endpoints

Nexgo may provide notice for material breaking changes where reasonably practicable.

You are responsible for maintaining your integration.

22API Versioning

Nexgo may provide versioned APIs.

For example: v1, v2, v3.

You should use the version specified in Nexgo's current API documentation.

Nexgo may eventually deprecate older API versions.

Where applicable, Nexgo may provide a migration period before discontinuing an older version.

23API Availability

Nexgo aims to maintain reliable API availability but does not guarantee that APIs will always be:

• Available
• Uninterrupted
• Error-free
• Free from latency
• Free from maintenance periods
• Nexgo may temporarily restrict API availability for:
• Maintenance
• Security
• Upgrades
• Emergency situations
• Infrastructure changes
• Regulatory requirements

24API Errors

API responses may include errors caused by:

• Invalid authentication
• Invalid parameters
• Missing information
• Unauthorized access
• Rate limits
• Service unavailability
• Shipment status restrictions
• Courier Partner errors
• Other technical or operational conditions

Your application must handle API errors appropriately.

25Courier Partner Data

Some API responses may contain information received from third-party Courier Partners.

Such information may:

• Change over time
• Be delayed
• Be incomplete
• Be subject to Courier Partner systems
• Be unavailable temporarily

Nexgo does not guarantee that all third-party information will always be accurate or available in real time.

26API Charges

Nexgo may charge fees for certain API usage or services.

Applicable charges may include:

• API subscription fees
• Transaction fees
• Shipment charges
• Premium API charges
• Excess usage charges
• Other applicable fees

Any applicable pricing will be communicated through the relevant commercial plan, rate card or agreement.

27No Circumvention

You must not use APIs or technical methods to circumvent:

• Shipping charges
• Account restrictions
• Rate limits
• Courier restrictions
• Subscription limits
• Security controls
• Usage limits
• Other Nexgo controls

Attempts to circumvent such controls may result in immediate suspension.

28Security Testing

You must not conduct penetration testing, vulnerability scanning, load testing or other security testing against Nexgo APIs without prior written authorization.

If you identify a security vulnerability, report it to:

Security email

nexgo201@gmail.com

Please do not publicly disclose the vulnerability before Nexgo has had a reasonable opportunity to investigate and address it.

29Intellectual Property

Nexgo retains all rights in:

• APIs
• API architecture
• Documentation
• SDKs
• Software
• Endpoints
• Data structures
• Nexgo trademarks
• Nexgo branding

Your use of the API does not transfer ownership of Nexgo intellectual property to you.

30SDKs and Developer Tools

Where Nexgo provides SDKs, libraries or developer tools, they are provided for authorized integration purposes.

You must not:

• Modify them to bypass security
• Remove license notices
• Redistribute proprietary components without permission
• Use them for unlawful purposes

31Branding

You may not represent your application or service as being owned, operated or officially endorsed by Nexgo unless Nexgo has provided written authorization.

Use of the Nexgo name, logo or trademarks must comply with Nexgo's brand guidelines.

32API Suspension

Nexgo may suspend API access if:

• Credentials are compromised
• Unusual traffic is detected
• Rate limits are repeatedly violated
• Security risks are identified
• Fraud is suspected
• The account violates these Terms
• Payments remain overdue
• Required KYC is incomplete
• The API is used unlawfully
• Suspension is required for security or compliance

Nexgo may restore access after the relevant issue has been resolved.

33API Termination

Nexgo may terminate API access or discontinue an API where reasonably necessary.

Upon termination, you must:

• Stop making API requests
• Stop using Nexgo credentials
• Remove credentials from your systems
• Stop representing the integration as active
• Handle stored data according to applicable requirements

Termination does not remove outstanding financial or legal obligations.

34Indemnification

You agree to indemnify and hold harmless Nexgo, its affiliates, officers, employees, agents and service providers against claims, losses, damages, liabilities and expenses arising from:

• Your API usage
• Your violation of these API Terms
• Unauthorized access caused by your security failure
• Misuse of customer information
• Fraudulent API activity
• Violation of applicable law
• Your application or integration
• Intellectual property infringement
• Unauthorized use of Nexgo data

35Limitation of Liability

To the maximum extent permitted by applicable law, Nexgo shall not be liable for indirect, incidental, special, consequential or punitive damages arising from API use.

Nexgo shall not be responsible for losses caused solely by:

• Your application
• Your infrastructure
• Third-party integrations
• Internet connectivity
• Courier Partner systems
• Incorrect API implementation
• Failure to securely store credentials

Nothing in these API Terms excludes liability that cannot legally be excluded.

36Confidentiality

Information exchanged through the Nexgo API that is confidential or reasonably understood to be confidential must be protected from unauthorized disclosure.

You must not disclose confidential Nexgo technical information except to authorized personnel who need it for the integration.

37Compliance With Laws

You must use Nexgo APIs in compliance with all applicable laws and regulations, including those relating to:

• Data protection
• Privacy
• Cybersecurity
• Consumer protection
• Taxation
• Logistics
• E-commerce
• Telecommunications
• Fraud prevention

You are responsible for determining which laws apply to your business.

38Changes to API Terms

Nexgo may update these API Terms from time to time.

The latest version will be published on the Nexgo website or developer portal.

Where required, Nexgo may provide notice of material changes.

Continued API usage after the effective date of updated Terms constitutes acceptance of the revised Terms, to the extent permitted by law.

39Governing Law

These API Terms shall be governed by the laws of India.

Subject to applicable law, courts located in [CITY, STATE, INDIA] shall have jurisdiction.

40Dispute Resolution

The parties will first attempt to resolve disputes through good-faith discussions.

If the dispute cannot be resolved amicably, it may be referred to arbitration in accordance with applicable Indian law.

Seat of arbitration

[CITY, INDIA]

Language

English

Number of arbitrators

One

41Relationship With Other Nexgo Policies

These API Terms should be read together with:

• Nexgo Terms of Service
• Nexgo Privacy Policy
• Nexgo Cookie Policy
• Nexgo Merchant Agreement
• Nexgo Prohibited Items Policy
• Nexgo Claims Policy
• Nexgo Shipping & Packaging SOP
• Nexgo API Documentation
• Applicable pricing/rate card

If there is a conflict, the specific agreement or API documentation applicable to the relevant service may prevail to the extent stated therein.

42Acceptance

By requesting API access, generating API credentials, connecting your application to Nexgo, or making API requests, you acknowledge that you have read, understood and accepted these API Terms of Use.