Rocket APIs allow traders and developers to create their own trading and investment platforms or customize the user experience on the Rocket Platform. This guide provides detailed information on the terms and conditions, usage guidelines, and other important aspects of using Rocket APIs provided by Navia Markets Ltd.

1. Introduction

• Navia Markets Ltd (Navia) offers API services to its clients for building customized trading platforms.
• Location: Ganga Griha, 4th & 5th Floor, No.9, Nungambakkam High Road, Chennai – 600 034.
• SEBI Registration: INZ000095034

2. Terms and Conditions

a) API Access & Usage:

• Purpose: Rocket APIs are designed for building innovative investment and trading platforms (IBT) that increase capital market participation in India.
• API Access: Clients can access APIs for personal use or to build platforms offered to the public.
• Limits: Navia may impose usage limits to ensure API stability.
• Monitoring: Navia reserves the right to monitor, track, and record all API interactions to maintain security and reliability.

b) Compliance & Restrictions:

• Regulations: All API-enabled platforms must comply with SEBI and exchange regulations. Necessary approvals must be obtained where applicable.
• Automated Trades: APIs are not intended for fully automated trading without manual intervention. Required approvals must be sought for such use.

c) Subscription & Charges:

• API Types:
  • Market Data API
  • Interactive API
• Subscription Cost: ₹1500 + GST per API, per month.
• Subscription Renewal: Auto-debited from the trading account on the 28th day from the initial subscription date.
• Non-Refundable: API charges are non-refundable.
• Revenue Sharing: Possible revenue-sharing arrangements may be discussed with Navia, subject to SEBI and exchange guidelines.

d) Liability & Termination:

• Uptime: API response times may vary due to factors like market conditions and technical issues.
• No Warranties: Navia disclaims any guarantees regarding API performance.
• Termination: Navia may terminate API access for non-compliance with terms. Clients can also terminate access by providing written notice.

3. Registration and Compliance

a) Entity-Level Acceptance: Clients using APIs on behalf of an entity must have the authority to bind the entity to the API terms.

b) Registration Process: Registration may require providing identification and contact details. Clients must keep this information accurate and up-to-date.

4. Confidentiality and Privacy

a) API Usage:

• Prohibited Actions: APIs may not be sublicensed, used to introduce malware, reverse-engineered, or used to invade user privacy.
• Credentials: Clients must keep their API credentials confidential.

b) User Data: : API users must adhere to Navia’s privacy policy and all applicable privacy laws.

5. Governing Law

a) Jurisdiction: The agreement is governed by the laws of India, with jurisdiction in Chennai, Tamil Nadu.

b) No Partnership or Agency: Navia does not form partnerships or agencies with API users and reserves the right to terminate API access for non-compliance with SEBI regulations.