Legal

Terms & Conditions

The agreement that governs your use of IRCTC API. Last updated 16 October 2026.

Terms of Service

01Acceptance of Terms

  • By accessing, purchasing, or using IRCTC API, you agree to be bound by these Terms and Conditions.
  • If you do not agree with any part of these Terms, you must immediately discontinue use of the Service.
  • Continued use of IRCTC API following any modification of these Terms constitutes acceptance of the revised Terms.

02Independent Service Disclaimer

  • IRCTC API is an independent developer platform.
  • IRCTC API is not affiliated with, endorsed by, authorized by, sponsored by, or officially connected with Indian Railways, IRCTC, CRIS, the Government of India, or any railway authority.
  • IRCTC API is not an official source of railway information.
  • Users must independently verify information before relying upon it for operational, financial, legal, regulatory, commercial, or customer-facing purposes.
  • Use of IRCTC API does not imply any relationship with or approval from any government organization.

03Service Description

  • IRCTC API provides APIs, developer tools, and related services that aggregate, process, and present railway-related information in a developer-friendly format.
  • The Service is intended primarily for developers, experimentation, learning, prototyping, and lightweight integrations.
  • Access to IRCTC API does not transfer ownership of any software, infrastructure, documentation, intellectual property, or service components.

04API License

  • IRCTC API grants a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to access and use the Service.
  • The license remains valid only while the user's account is active and compliant with these Terms.
  • All rights not expressly granted are reserved by IRCTC API.

05API Key Security

  • API keys are issued to individual accounts and must remain confidential.
  • Users may not share, transfer, lease, sell, sublicense, publish, or distribute API keys.
  • Users are solely responsible for all activity performed using their API keys.
  • Users must immediately notify IRCTC API of any suspected unauthorized access or compromise.

06Commercial Usage

  • Commercial usage is permitted only through an active paid subscription.
  • IRCTC API is an independent developer project and is not marketed as enterprise-grade infrastructure.
  • Businesses integrating IRCTC API do so entirely at their own risk.
  • IRCTC API makes no guarantees regarding suitability for commercial operations, business continuity, compliance requirements, customer obligations, production workloads, or operational decision-making.
  • Users are solely responsible for determining whether IRCTC API is appropriate for their intended use.

07Prohibited Uses

  • Reselling API access, API responses, or any IRCTC API-derived service.
  • Redistributing IRCTC API data to third parties.
  • Providing IRCTC API responses through another API, platform, product, or service.
  • Creating a competing railway information service or API.
  • Building derivative products whose primary value is IRCTC API data.
  • Sharing API keys with customers, clients, partners, contractors, or other organizations.
  • Creating multiple accounts to bypass quotas, restrictions, pricing, or enforcement actions.
  • Attempting to circumvent authentication systems, security controls, quotas, or rate limits.
  • Reverse engineering, probing, testing, or attempting to discover internal implementation details.
  • Using IRCTC API for unlawful, fraudulent, deceptive, abusive, or unauthorized purposes.

08Data Usage and Storage Restrictions

  • Users may not create, maintain, replicate, enrich, archive, export, mirror, scrape, or distribute databases derived substantially from IRCTC API data.
  • Users may not use IRCTC API as a source for building permanent railway information repositories.
  • Users may not create historical datasets, commercial archives, analytics warehouses, or large-scale repositories derived primarily from IRCTC API data.
  • Long-term retention of IRCTC API data is prohibited except for temporary application functionality.
  • Temporary caching is permitted only to improve application performance and must not be used to avoid API usage.
  • Stored data may not be redistributed, resold, licensed, exposed through another service, or made publicly available.
  • IRCTC API reserves sole discretion in determining whether a user's storage or caching practices violate these Terms.

09Acceptable Use of Data

  • IRCTC API data may only be used within applications owned or operated by the subscribing user.
  • Users may not expose bulk data feeds, downloadable datasets, public APIs, exports, or derivative services primarily based on IRCTC API data.
  • Users may not use IRCTC API data to create competing platforms, marketplaces, aggregators, analytics products, or commercial data repositories.

10Rate Limits and Fair Usage

  • All plans are subject to request limits, quotas, fair usage requirements, and technical restrictions.
  • Rate limits may be enforced per API key, account, IP address, application, organization, or other identifiers.
  • IRCTC API may throttle, restrict, suspend, or terminate access where usage adversely affects service stability or violates fair usage policies.
  • Unused request quotas do not carry over unless explicitly stated.

11Subscription Plans & Request Packs

  • Legacy paid subscriptions remain valid under their original terms. New plans are available monthly or annually as shown at checkout.
  • New annual plans are paid upfront for twelve (12) months; included request quota renews monthly during that term.
  • Request Packs are add-ons available only for an active paid subscription and are not standalone products.
  • Purchasing a Request Pack increases the API request quota available under the associated active paid subscription.
  • A Request Pack purchase does not renew, extend, or otherwise modify the subscription's validity period.
  • All unused requests from a Request Pack automatically expire when the associated paid subscription expires.
  • When a paid subscription expires, the account reverts to the Free plan and all remaining Request Pack requests are permanently forfeited.
  • Purchasing a new subscription does not restore or carry forward Request Pack requests that expired with a previous subscription.
  • Users are responsible for ensuring that sufficient subscription validity remains before purchasing a Request Pack.
  • Request Pack purchases are non-refundable after successful payment, except where required by applicable law.

12Security and Suspicious Activity

  • IRCTC API may monitor service activity for security, fraud prevention, abuse detection, compliance, and operational purposes.
  • Any suspicious, abusive, fraudulent, unauthorized, or potentially harmful activity may result in immediate restriction, suspension, or termination.
  • Examples include credential sharing, unusual request patterns, scraping, quota abuse, automated account creation, resale attempts, data harvesting, or security violations.
  • Users may be required to provide additional verification during investigations.
  • IRCTC API reserves sole discretion in determining whether activity is suspicious or abusive.

13Account Suspension and Termination

  • IRCTC API may suspend, restrict, disable, or terminate accounts without prior notice.
  • Violations involving resale, redistribution, key sharing, abuse, data extraction, suspicious activity, or breaches of these Terms may result in immediate termination.
  • All licenses and access rights immediately cease upon termination.
  • Associated API keys, accounts, IP addresses, domains, applications, organizations, and related resources may also be blocked.

14Payments and Refunds

  • All payments are final.
  • Subscriptions, credits, and usage fees are non-refundable unless required by applicable law.
  • Unused requests, quotas, or subscription periods are non-refundable.
  • No refunds will be provided for suspensions or terminations resulting from violations of these Terms.
  • Users are responsible for evaluating the Service before purchasing a subscription.
  • Chargebacks, payment fraud, or abusive dispute activity may result in immediate account termination.

15Third-Party Data Sources

  • IRCTC API may rely on third-party systems, publicly available information, external services, and infrastructure providers.
  • IRCTC API does not control such third-party sources and cannot guarantee their availability, continuity, legality, accuracy, completeness, or future accessibility.
  • Changes made by third-party providers may affect IRCTC API without notice.
  • IRCTC API is not responsible for inaccuracies, interruptions, delays, or failures resulting from third-party systems.

16Service Availability

  • IRCTC API is provided on a best-effort basis.
  • No service level agreement (SLA), uptime commitment, availability guarantee, reliability guarantee, or response-time guarantee is provided unless explicitly agreed in writing.
  • Maintenance, outages, upgrades, infrastructure failures, data source changes, technical issues, force majeure events, or third-party failures may affect service availability.
  • The Service may become unavailable at any time without prior notice.

17Business Dependency Disclaimer

  • Users must not treat IRCTC API as their sole source of operationally critical railway information.
  • Users are responsible for maintaining backup systems, fallback providers, alternative solutions, and contingency plans where business continuity is important.
  • IRCTC API shall not be responsible for losses arising from outages, service interruptions, reduced availability, data changes, or service discontinuation.
  • Users acknowledge that IRCTC API may be modified, restricted, suspended, or discontinued at any time.

18Service Modifications and Discontinuation

  • IRCTC API reserves the right to modify, suspend, restrict, replace, remove, or discontinue any feature, endpoint, API version, pricing plan, subscription tier, or service component at any time.
  • IRCTC API has no obligation to continue operating any part of the Service indefinitely.
  • No compensation, migration assistance, replacement services, consulting services, source code access, technical support, or continued operation shall be owed following service modifications or discontinuation except where required by law.

19Intellectual Property

  • All IRCTC API software, APIs, branding, documentation, infrastructure, website content, designs, logos, and platform components are protected by applicable intellectual property laws.
  • No ownership rights are transferred through use of the Service.
  • Users may not copy, reproduce, distribute, modify, or create derivative works from IRCTC API except as expressly permitted.

20Disclaimer of Warranties

  • The Service is provided on an 'AS IS' and 'AS AVAILABLE' basis.
  • IRCTC API expressly disclaims all warranties, whether express, implied, statutory, or otherwise.
  • IRCTC API does not guarantee accuracy, completeness, reliability, availability, suitability, performance, or fitness for any particular purpose.
  • Users assume all risks associated with use of the Service.

21Limitation of Liability

  • To the maximum extent permitted by law, IRCTC API and its owner shall not be liable for any direct, indirect, incidental, consequential, special, exemplary, punitive, or economic damages.
  • This includes loss of revenue, profits, business opportunities, customers, goodwill, data, contracts, operational capability, or business continuity.
  • IRCTC API shall not be liable for decisions made based on information obtained through the Service.
  • In all circumstances, IRCTC API's total aggregate liability shall not exceed the amount paid by the user to IRCTC API during the thirty (30) days preceding the event giving rise to the claim.

22Indemnification

  • Users agree to defend, indemnify, and hold harmless IRCTC API and its owner from any claims, liabilities, damages, losses, expenses, legal costs, or demands arising from their use of the Service, violation of these Terms, misuse of API data, or infringement of third-party rights.

23No Agency Relationship

  • Nothing in these Terms creates any partnership, joint venture, employment relationship, agency relationship, franchise relationship, or official representation between IRCTC API and any user.
  • Users may not represent themselves as official partners, distributors, agents, or representatives of IRCTC API.

24Changes to Terms

  • IRCTC API may update these Terms at any time.
  • Changes become effective upon publication.
  • Continued use of the Service after publication constitutes acceptance of the revised Terms.

25Governing Law

  • These Terms shall be governed by and construed in accordance with the laws of India.
  • Any disputes arising from or relating to the Service shall be subject to the exclusive jurisdiction of the courts located in West Bengal, India.
  • Mandatory consumer protection rights under applicable law shall remain unaffected where legally required.