Free API Terms of Use Template
These API terms of use are for a company that offers a public API to developers at no charge. They are drafted from the provider's side: developers may use the API commercially, but rate limits are set at the provider's discretion, every use must credit the provider by name with a link, there is no warranty or uptime promise, liability is excluded entirely to the extent the law permits, and access can be suspended for misuse. The provider gives 30 days' notice before deprecating or materially changing the API, and developers may send end-user personal data through it.
Use them when you open an API to the public to grow adoption of your product, data or platform, and want developers to build freely while you keep control over capacity, branding and risk. Because nothing is paid, the terms lean on attribution and fair use rather than fees.
The terms have 18 sections. Acceptance and Scope of Terms and Account Registration and API Credentials explain who is bound and how keys are issued. License Grant and Permitted Commercial Use sets what developers may build. Restrictions and Prohibited Conduct lists what they must not do. Rate Limits and Fair Use Policy keeps limits with the provider. Attribution Requirements sets the credit and link. Data Protection and End-User Personal Data covers personal data sent through the API. Intellectual Property Rights and Feedback protects the provider. Modifications, Versioning, and Deprecation of the API sets the 30-day notice. Disclaimer of Warranties and Service Availability and Exclusion of Liability remove the provider's risk, and Indemnification shifts claims to developers. Suspension of Access for Misuse, Term, Termination, and Effects of Termination, Amendments to These Terms and the closing provisions complete them.
Fill in your company name, the API name, the attribution wording, the link to your privacy policy and how you publish rate limits. Keep a changelog, so developers can see what changed and when. The governing law is deliberately left blank, so the terms can be adapted to your country.
It is a template, not legal advice.
FREE API TERMS OF USE
These Free API Terms of Use (the "Terms") are effective as of [Effective Date] (the "Effective Date") and are issued by [Provider Legal Name], a [type of legal entity] organized and existing under the laws of [jurisdiction of organization], having its registered office at [Provider Address] and registered under number [Registration Number] (the "Provider").
These Terms are addressed to any person or entity that registers for, obtains credentials for, or otherwise accesses or uses the Provider's application programming interface and who thereby becomes a party to these Terms (the "Developer"). The Provider and the Developer are each referred to as a "Party" and together as the "Parties."
The Provider operates a business in the software industry and makes available, at no charge, a public application programming interface known as [API Name], together with related documentation, tools, and resources, for the purpose of enabling developers to build software applications, products, and services that interoperate with the Provider's systems.
The Provider is willing to make the API available to the Developer on a free-of-charge basis solely on the terms and subject to the conditions set out in these Terms, and the Developer wishes to use the API on those terms and conditions.
These Terms are published at [URL of Terms] and are not subject to individual negotiation. The Developer's registration for, or use of, the API constitutes acceptance of these Terms in their entirety. The Provider may be contacted regarding these Terms at [Provider Contact Email] or [Provider Notice Address].
Definitions and Interpretation
In these Terms, the following capitalized words and expressions have the meanings set out below, unless the context requires otherwise.
"API" means the application programming interface known as [API Name] made available by the Provider, including all endpoints, methods, protocols, software libraries, software development kits, sandbox environments, and any updates, versions, or successors thereto that the Provider makes available under these Terms.
"API Credentials" means the API keys, tokens, client identifiers, secrets, passwords, and any other authentication or authorization codes issued by the Provider to the Developer, or generated through the Developer Account, to enable access to the API.
"API Content" means all data, responses, results, text, images, metadata, and other content made available through the API by the Provider or its licensors, excluding End-User Data and Developer Materials.
"Application" means any software application, website, product, service, or system developed, operated, or made available by or on behalf of the Developer that accesses, calls, or integrates with the API.
"Developer Account" means the account registered by the Developer with the Provider that enables the Developer to obtain API Credentials and to access the API.
"Developer Materials" means the Application and all software, content, trademarks, and other materials owned or controlled by the Developer, excluding the API and the API Content.
"Documentation" means the technical documentation, guides, specifications, policies, and instructions relating to the API that the Provider publishes or makes available from time to time at [Documentation URL] or by other means.
"End User" means any natural person who uses, or whose information is processed through, an Application.
"End-User Data" means any information relating to an identified or identifiable End User, including any personal data, that is transmitted to the API by or on behalf of the Developer or that is returned in responses from the API in connection with the Developer's use of the API.
"Applicable Law" means all laws, regulations, binding orders, and governmental requirements applicable to a Party or to the activities contemplated by these Terms, including data protection, privacy, export control, and sanctions laws.
"Rate Limits" means any limit, quota, threshold, throttle, or other restriction on the number, frequency, volume, size, or type of requests or the amount of data that may be submitted to or retrieved from the API, as determined by the Provider from time to time.
"Feedback" means any suggestions, comments, ideas, enhancement requests, bug reports, or other input relating to the API that the Developer provides to the Provider.
In these Terms, headings are for convenience only and do not affect interpretation. The words "including" and "includes" mean "including without limitation." References to a section or clause are references to a section or clause of these Terms. References to a statute or law include that law as amended or replaced from time to time. The singular includes the plural and vice versa. No provision shall be construed against the Provider by reason of the Provider having drafted these Terms.
Acceptance and Scope of Terms
These Terms govern the Developer's access to and use of the API, the API Content, and the Documentation, and constitute a legally binding agreement between the Provider and the Developer.
The Developer accepts these Terms upon the earliest of: (a) clicking an "I Agree" button or checking a box indicating acceptance; (b) registering a Developer Account; (c) obtaining or using any API Credentials; or (d) otherwise accessing or using the API.
If the Developer accepts these Terms on behalf of a company, organization, or other legal entity, the Developer represents and warrants that it has full authority to bind that entity to these Terms, and in that case "Developer" refers to that entity. If the Developer lacks such authority, the Developer must not access or use the API.
The Developer represents and warrants that it is of legal age to enter into a binding contract under Applicable Law, has not previously been barred from using the Provider's services, and is not located in, or a national or resident of, any jurisdiction, or listed on any list of restricted persons, that would make the Developer's use of the API unlawful.
These Terms incorporate the Documentation and any supplementary policies published by the Provider and referenced in these Terms, including any acceptable use or branding guidelines located at [Policies URL] (together, the "Supplemental Policies"). In the event of a conflict, these Terms prevail over the Supplemental Policies unless the Supplemental Policies expressly state otherwise.
These Terms constitute the entire agreement between the Parties regarding the subject matter hereof and supersede all prior or contemporaneous understandings relating to the API. If the Developer and the Provider have executed a separate written agreement expressly governing the Developer's use of the API, that agreement prevails to the extent of any conflict.
If the Developer does not agree to these Terms in their entirety, the Developer must not register for, access, or use the API.
Account Registration and API Credentials
To access the API, the Developer must register a Developer Account by providing the information requested by the Provider, including [required registration information]. The Developer shall ensure that all registration information is accurate, current, and complete, and shall promptly update it as necessary.
The Provider may, in its sole discretion, accept or reject any registration, limit the number of Developer Accounts or API Credentials that the Developer may hold, and require verification of identity or of the intended use of the API, in each case without obligation to give reasons.
The API Credentials are issued to the Developer for its exclusive use, are confidential, and are the property of the Provider. The Developer shall not share, sell, transfer, sublicense, publish, or otherwise disclose API Credentials to any third party, and shall not embed API Credentials in any publicly accessible code, repository, or client-side environment where they may be extracted by others.
The Developer shall safeguard the API Credentials using industry-standard security measures and is solely responsible for all activity occurring under its Developer Account and API Credentials, whether or not authorized by the Developer. The Developer shall notify the Provider without undue delay at [Security Contact Email] upon becoming aware of any loss, theft, compromise, or unauthorized use of API Credentials or the Developer Account.
The Provider may revoke, suspend, rotate, regenerate, or reissue any API Credentials at any time, with or without notice, for security, operational, or administrative reasons or for any breach or suspected breach of these Terms.
The Developer shall not create multiple Developer Accounts or obtain multiple sets of API Credentials for the purpose of circumventing Rate Limits, restrictions, suspensions, or other controls imposed by the Provider.
The Developer Account may not be assigned or transferred without the prior written consent of the Provider. Any purported transfer in violation of this clause is void.
License Grant and Permitted Commercial Use
Subject to the Developer's continuing compliance with these Terms, the Provider grants the Developer a limited, non-exclusive, non-transferable, non-sublicensable (except as expressly permitted in this section), revocable, royalty-free license during the term of these Terms to access and use the API, the API Content, and the Documentation solely to develop, test, operate, and support Applications within the territory of [Territory].
The Developer may use the API in Applications that are made available to End Users and third parties for commercial purposes, including Applications that are sold, licensed, or monetized by the Developer through subscriptions, advertising, or other commercial models, provided that such use complies with these Terms, the Documentation, and Applicable Law.
The Developer may display, cache, and store API Content solely to the extent and for the duration permitted by the Documentation or, if the Documentation is silent, solely as is reasonably necessary for the proper operation of the Application and for no longer than [maximum caching period]. The Developer shall refresh or delete cached API Content upon the Provider's reasonable request or where the API indicates that such content has been updated or removed.
The Developer may permit its authorized employees and contractors to use the API on its behalf, provided that they are bound by written obligations no less protective of the Provider than these Terms and that the Developer remains fully responsible for their acts and omissions as if they were its own.
The Developer shall not use the API to build or offer a product or service that is substantially similar to, or that competes with, the API or the Provider's core products or services, except as the Provider may expressly authorize in writing at [Provider Contact Email].
The commercial use permitted under these Terms does not entitle the Developer to any fee waiver, service level, priority treatment, support, or other commitment from the Provider. The API is provided free of charge, and the Provider may, in its sole discretion, introduce paid plans or tiers in the future in accordance with the section governing amendments.
All rights not expressly granted to the Developer in these Terms are reserved by the Provider. No license or right is granted by implication, estoppel, or otherwise.
Restrictions and Prohibited Conduct
The Developer shall not, and shall not permit, authorize, or assist any third party to: (a) copy, modify, translate, or create derivative works of the API, the API Content, or the Documentation, except as expressly permitted by these Terms; (b) reverse engineer, decompile, disassemble, or otherwise attempt to derive the source code, algorithms, or underlying structure of the API; or (c) sell, rent, lease, sublicense, distribute, or otherwise make the API available to any third party on a standalone basis or as a substitute for the API.
The Developer shall not use the API: (a) in violation of Applicable Law or the rights of any third party, including intellectual property, privacy, and publicity rights; (b) to transmit, store, or distribute any content that is unlawful, defamatory, obscene, harassing, discriminatory, or otherwise objectionable; or (c) in any manner that is deceptive, fraudulent, or misleading.
The Developer shall not introduce into the API or the Provider's systems any virus, malware, ransomware, worm, time bomb, or other harmful or malicious code, or engage in any activity that interferes with, disrupts, degrades, or imposes an unreasonable or disproportionate load on the API or the Provider's infrastructure.
The Developer shall not probe, scan, or test the vulnerability of the API or the Provider's systems, breach or circumvent any authentication, security, or access control measure, or access the API by any means other than the interfaces and API Credentials provided by the Provider, except as expressly authorized in writing by the Provider.
The Developer shall not use the API or API Content to train, fine-tune, or develop any machine learning or artificial intelligence model, or to bulk extract, scrape, harvest, or build a database or index of API Content, except to the extent expressly permitted by the Documentation or authorized in writing by the Provider.
The Developer shall not remove, obscure, or alter any proprietary notices, attribution, or labels of the Provider or its licensors in the API, the API Content, or the Documentation, nor represent that the Application is endorsed by, sponsored by, or affiliated with the Provider unless the Provider has so agreed in writing.
The Developer shall not use the API in any high-risk environment where failure or inaccuracy could lead to death, personal injury, or severe physical or environmental damage, including the operation of critical infrastructure, life-support systems, or weapons systems.
The Developer shall not use the API in any manner that violates export control, sanctions, or trade restrictions under Applicable Law.
Rate Limits and Fair Use Policy
The Provider may establish and modify Rate Limits at any time, in its sole and absolute discretion and without prior notice to the Developer. Rate Limits may differ among Developers, Developer Accounts, endpoints, or categories of use, and may be published in the Documentation, communicated in API responses, or applied without publication.
The Developer shall comply at all times with all Rate Limits, whether or not published, and shall design its Applications to handle rate-limiting responses and error messages gracefully, including by implementing appropriate backoff and retry logic.
The Provider may throttle, queue, delay, reject, or block requests that exceed or are reasonably believed to exceed any Rate Limit, and may do so without liability to the Developer. Any such action shall not constitute a breach of these Terms by the Provider.
The Developer shall use the API in a fair and reasonable manner consistent with its intended purpose as an API offered free of charge. The Provider may determine, in its sole discretion, whether any use is excessive, abusive, or inconsistent with fair use, taking into account factors including request volume, request patterns, resource consumption, and the effect of the use on other developers and on the Provider's systems.
The Developer shall not attempt to circumvent or evade Rate Limits by any means, including by rotating or pooling API Credentials, using multiple Developer Accounts, distributing requests across multiple IP addresses or systems, or using intermediaries or proxies.
The Developer may request increased limits by contacting the Provider at [Provider Contact Email]. The Provider has no obligation to grant such a request and may condition any increase on additional terms, including the payment of fees under a separate agreement at rates of [Fee Terms].
Attribution Requirements
The Developer shall display clear and conspicuous attribution to the Provider in each Application that uses the API or API Content, in the form of the Provider's name, "[Provider Brand Name]," accompanied by a functioning hyperlink to [Provider Attribution URL] (the "Attribution").
The Attribution shall be placed in a location that is reasonably visible to End Users, such as the Application's user interface, "About" or "Credits" page, website footer, or accompanying documentation, and shall be no less prominent than the attribution of any other third-party service used in the Application.
The Developer shall not modify, abbreviate, distort, or obscure the Attribution, nor display it in a manner that suggests that the Provider endorses, sponsors, or is affiliated with the Developer or the Application, except as the Provider may expressly approve in writing.
The Developer is granted a limited, non-exclusive, non-transferable, revocable license to use the Provider's name and, where the Provider supplies them, its logos and marks, solely for the purpose of displaying the Attribution in accordance with this section and any branding guidelines published by the Provider. All goodwill arising from such use inures solely to the Provider.
Where the Application does not have a visual interface, the Developer shall include the Attribution in the Application's public-facing documentation, repository description, or other equivalent location reasonably accessible to users of the Application.
The Provider may update the form of the Attribution from time to time by publishing the update in the Documentation, and the Developer shall implement the updated Attribution within [Attribution Update Period] following such publication.
The Provider may, at its discretion, publicly identify the Developer and the Application as a user of the API, including by using the Developer's name and logo, unless the Developer objects in writing to [Provider Contact Email].
Data Protection and End-User Personal Data
The Developer acknowledges that the Developer may transmit End-User Data to the API and that the API may return End-User Data in responses. The Developer shall not transmit any End-User Data to the API unless it is necessary for the intended operation of the Application and permitted by the Documentation.
As between the Parties, the Developer is the party responsible for determining the purposes and means of processing End-User Data in connection with its Application. The Developer shall comply with all Applicable Law relating to data protection, privacy, and electronic communications in connection with its collection, use, disclosure, transmission, and other processing of End-User Data.
The Developer represents and warrants that, before transmitting any End-User Data to the API, it has: (a) provided End Users with all notices required by Applicable Law, including a privacy policy that accurately discloses the transmission of End-User Data to the Provider as a service provider or processor; (b) obtained all consents, authorizations, and permissions required; and (c) established a valid legal basis for such processing and for any cross-border transfer of End-User Data.
The Developer shall not transmit to the API any special categories or sensitive categories of personal data, including data revealing health, biometric or genetic data, financial account or payment card information, government identifiers, precise geolocation, or data relating to children, unless the Documentation expressly permits and the Provider has expressly agreed in writing.
To the extent that the Provider processes End-User Data on behalf of the Developer through the API, the Provider shall process such data only on the Developer's documented instructions as expressed by its use of the API and these Terms, shall implement appropriate technical and organizational measures designed to protect such data, and shall treat such data as confidential. The Provider may engage subprocessors and may process data in [Processing Locations]. Where Applicable Law requires a separate data processing agreement, the Parties shall enter into one on the Provider's standard terms available at [Data Processing Terms URL].
The Provider may also process certain information relating to the Developer and its use of the API, including account details, usage logs, and technical data, as a controller for purposes including operating, securing, and improving the API, enforcing these Terms, and complying with legal obligations, in accordance with its privacy notice at [Provider Privacy Policy URL].
The Developer shall notify the Provider without undue delay at [Security Contact Email] upon becoming aware of any unauthorized access to or disclosure of End-User Data that affects or may affect the API, and shall cooperate reasonably with the Provider in investigating and remediating the matter. The Developer is solely responsible for any notifications to End Users and authorities that are required in relation to the Application.
The Developer shall reasonably assist, at its own cost, with any requests from End Users or authorities concerning End-User Data processed through the API, and the Provider may delete or return End-User Data upon termination in accordance with the section governing termination.
Intellectual Property Rights and Feedback
As between the Parties, the Provider and its licensors own and retain all right, title, and interest, including all intellectual property rights, in and to the API, the API Content, the Documentation, the Provider's names, logos, and marks, and all improvements, enhancements, modifications, and derivative works of any of the foregoing, whether or not made at the suggestion of the Developer. Nothing in these Terms transfers any ownership interest to the Developer.
As between the Parties, the Developer retains all right, title, and interest in and to the Developer Materials and, subject to the rights of End Users and third parties and the rights granted in these Terms, the End-User Data. The Developer grants the Provider a non-exclusive, worldwide, royalty-free license to host, process, transmit, reproduce, and use the Developer Materials and End-User Data submitted through the API solely as necessary to provide, secure, maintain, and support the API and to comply with Applicable Law.
The Developer grants the Provider a non-exclusive, perpetual, irrevocable, worldwide, royalty-free, fully paid-up, transferable, and sublicensable license to use, reproduce, modify, and otherwise exploit any Feedback for any purpose without attribution, compensation, or obligation to the Developer. Feedback shall not include End-User Data or Developer Materials other than as embodied in the Feedback itself.
The Developer represents and warrants that it has, and will maintain, all rights necessary to grant the licenses in this section and that the Developer Materials and End-User Data, and the Provider's processing of them in accordance with these Terms, do not and will not infringe or violate any third-party right or Applicable Law.
The Provider may collect and use aggregated, de-identified, or anonymized data relating to the use and performance of the API, which does not identify the Developer or any End User, for any lawful purpose, including analytics, benchmarking, security, and improvement of its products and services, and the Provider shall own all rights in such data.
The Developer shall promptly notify the Provider of any actual or suspected infringement or misappropriation of the Provider's intellectual property rights relating to the API that comes to its attention. The Provider has the sole right, but no obligation, to take enforcement action in relation to the API.
The Developer shall not register, or attempt to register, any trademark, domain name, or social media identifier that incorporates or is confusingly similar to the Provider's names or marks.
Modifications, Versioning, and Deprecation of the API
The Provider may modify, update, enhance, suspend, or discontinue the API or any part, version, feature, or endpoint of the API at any time, including by adding or removing functionality, changing the format, structure, or content of the API Content, or changing authentication methods.
The Provider may release new versions of the API and may designate prior versions as deprecated. The Developer is responsible for migrating the Application to the then-current version of the API within the timeframes specified in the Documentation or in notice from the Provider.
Except as provided in the following clauses, the Provider shall give the Developer not less than 30 days' prior notice before (a) permanently discontinuing the API as a whole or any generally available version or endpoint of it, or (b) making a material change to the API that is reasonably likely to cause the Developer's existing integrations to cease functioning without modification. Notice may be given by email to the address associated with the Developer Account, by notice in the Documentation or developer portal, or through the API itself, and is effective upon dispatch or publication.
The Provider may modify, suspend, or discontinue the API or any part of it immediately and without prior notice where the Provider reasonably determines that doing so is necessary to: (a) address security vulnerabilities or threats; (b) prevent or respond to abuse or misuse; (c) comply with Applicable Law, a court order, or a request of a governmental authority; (d) address third-party rights or claims; or (e) respond to circumstances beyond its reasonable control. The Provider shall use reasonable efforts to notify the Developer thereafter where practicable.
Bug fixes, security patches, performance improvements, additive changes (including new endpoints, fields, or optional parameters), changes to Rate Limits, and changes that are not reasonably likely to break existing integrations are not material changes for the purposes of the notice obligation above and may be made at any time without notice.
The Developer's continued use of the API following the effective date of any modification, deprecation, or discontinuation constitutes acceptance of the change. The Developer's sole and exclusive remedy in the event of any dissatisfaction with a change is to cease using the API.
The Provider shall have no obligation to provide support, maintenance, migration assistance, or continued availability of deprecated versions beyond the notice period stated in these Terms, and shall have no liability to the Developer or any End User arising from any modification, deprecation, or discontinuation made in accordance with this section.
Disclaimer of Warranties and Service Availability
THE API, THE API CONTENT, AND THE DOCUMENTATION ARE PROVIDED FREE OF CHARGE ON AN "AS IS" AND "AS AVAILABLE" BASIS, WITH ALL FAULTS, AND WITHOUT WARRANTIES OF ANY KIND. TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, THE PROVIDER AND ITS AFFILIATES, LICENSORS, AND SUPPLIERS DISCLAIM ALL WARRANTIES, CONDITIONS, AND REPRESENTATIONS, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, AND ANY WARRANTIES ARISING FROM COURSE OF DEALING, COURSE OF PERFORMANCE, OR USAGE OF TRADE.
THE PROVIDER DOES NOT WARRANT THAT THE API WILL BE AVAILABLE, UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE; THAT DEFECTS WILL BE CORRECTED; THAT THE API OR API CONTENT WILL BE ACCURATE, COMPLETE, RELIABLE, CURRENT, OR LAWFUL; OR THAT THE API WILL MEET THE DEVELOPER'S REQUIREMENTS OR BE COMPATIBLE WITH ANY APPLICATION, SYSTEM, OR DATA.
The Provider makes no commitment to any uptime, availability, latency, throughput, response time, or other service level, and no service level credits, refunds, or remedies shall apply. The API may be unavailable or degraded at any time, with or without notice, including due to maintenance, upgrades, failures, capacity constraints, third-party service interruptions, or events beyond the Provider's reasonable control.
The Developer acknowledges that the API is made available free of charge and that the Provider would not make the API available on these terms without the disclaimers and limitations in these Terms. The Developer is solely responsible for implementing appropriate redundancy, backup, error handling, and contingency measures in the Application so that any unavailability, interruption, or change of the API does not cause loss or harm to the Developer or to End Users.
The Provider provides no support for the API unless it expressly agrees otherwise in writing. Any support or assistance that the Provider may elect to provide is voluntary, may be withdrawn at any time, and is subject to these Terms.
No advice or information, whether oral or written, obtained by the Developer from the Provider or through the API shall create any warranty not expressly stated in these Terms. The Developer relies on the API and API Content at its own risk and is solely responsible for verifying the suitability and accuracy of any API Content before relying on it.
Where Applicable Law does not permit the exclusion of certain warranties, such warranties are limited to the minimum extent and shortest duration permitted by Applicable Law.
Exclusion of Liability
TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, THE PROVIDER AND ITS AFFILIATES, DIRECTORS, OFFICERS, EMPLOYEES, AGENTS, LICENSORS, AND SUPPLIERS (THE "PROVIDER PARTIES") SHALL NOT BE LIABLE TO THE DEVELOPER OR TO ANY PERSON CLAIMING THROUGH THE DEVELOPER, INCLUDING ANY END USER, FOR ANY LOSS OR DAMAGE OF ANY KIND ARISING OUT OF OR IN CONNECTION WITH THESE TERMS, THE API, THE API CONTENT, OR THE DOCUMENTATION, INCLUDING ANY ACCESS TO, USE OF, INABILITY TO USE, OR RELIANCE ON THEM.
WITHOUT LIMITING THE FOREGOING, TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, THE PROVIDER PARTIES EXCLUDE ALL LIABILITY FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, AND PUNITIVE DAMAGES, AND FOR LOSS OF PROFITS, REVENUE, BUSINESS, GOODWILL, ANTICIPATED SAVINGS, OR OPPORTUNITY, LOSS OR CORRUPTION OF DATA, COSTS OF PROCUREMENT OF SUBSTITUTE SERVICES, OR BUSINESS INTERRUPTION, HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, INCLUDING CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, MISREPRESENTATION, OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
The exclusions in this section apply to losses arising from any suspension, modification, deprecation, or discontinuation of the API or the Developer Account, any Rate Limit, any unauthorized access to or alteration of the Developer's data or transmissions, any error, omission, or inaccuracy in the API Content, and any act or omission of any third party.
The Developer acknowledges that the API is provided free of charge, that the exclusions and limitations in these Terms reflect a reasonable allocation of risk between the Parties, and that they form an essential basis of the Provider's decision to make the API available. The exclusions shall apply even if any limited remedy fails of its essential purpose.
Nothing in these Terms excludes or limits any liability that cannot be excluded or limited under Applicable Law. To the extent that liability cannot be fully excluded under Applicable Law, the aggregate liability of the Provider Parties, taken together, for all claims arising out of or relating to these Terms shall not exceed the lesser of the amount actually paid by the Developer to the Provider for the API in the 12 months preceding the first event giving rise to liability, which the Parties acknowledge is zero, and [Maximum Liability Amount].
Each provision of this section is separate and severable. If any part is held unenforceable, the remaining parts continue in full force, and the relevant part shall be enforced to the maximum extent permitted by Applicable Law.
The Developer shall not bring any claim against the Provider Parties arising out of or relating to these Terms or the API more than [Claim Period] after the cause of action arose, to the extent permitted by Applicable Law.
Indemnification
The Developer shall defend, indemnify, and hold harmless the Provider, its affiliates, and their respective directors, officers, employees, agents, licensors, successors, and assigns (the "Indemnified Parties") from and against any and all claims, demands, actions, suits, proceedings, investigations, losses, liabilities, damages, judgments, settlements, fines, penalties, costs, and expenses, including reasonable attorneys' fees and costs of investigation (collectively, "Claims"), arising out of or relating to any of the following.
The Claims covered include those arising out of or relating to: (a) the Developer's or its personnel's access to or use of the API, the API Content, or the Documentation; (b) the Application, including its development, operation, marketing, distribution, and monetization; (c) any breach of these Terms or of any representation or warranty given by the Developer; (d) the Developer Materials or End-User Data, including any allegation that they infringe or misappropriate any third-party right; and (e) any violation of Applicable Law by the Developer.
The Developer's indemnification obligations also extend to any Claims by End Users, regulatory authorities, or other third parties relating to the collection, use, disclosure, or transmission of End-User Data in connection with the Application, including any failure to provide required notices or obtain required consents.
The Provider shall give the Developer prompt written notice of any Claim for which it seeks indemnification, provided that any delay or failure to give notice shall relieve the Developer of its obligations only to the extent it is materially prejudiced by the delay or failure. The Provider may participate in the defense with counsel of its own choosing at its own expense.
The Developer shall not settle any Claim without the prior written consent of the Provider where the settlement imposes any obligation or liability on, or includes any admission by, an Indemnified Party, or does not include a full release of the Indemnified Parties. The Provider may assume control of the defense and settlement of any Claim at the Developer's expense where the Developer fails to assume the defense diligently or where the Claim involves the Provider's intellectual property, regulatory interests, or its other developers.
The Provider has no obligation to indemnify the Developer in connection with these Terms. The Developer's obligations under this section survive the termination or expiry of these Terms.
Suspension of Access for Misuse
The Provider may, at any time and in its sole discretion, with or without notice, suspend, restrict, or disable the Developer's access to the API, the Developer Account, or any API Credentials, in whole or in part, where the Provider reasonably believes or suspects that: (a) the Developer has breached or is likely to breach these Terms, the Documentation, or any Supplemental Policy; (b) the Developer's use of the API poses a security risk or may harm the API, the Provider's systems, other developers, or End Users; or (c) the Developer's use of the API may expose the Provider to legal or regulatory liability or reputational harm.
Without limiting the foregoing, the Provider may suspend access without prior notice where the Developer: (a) exceeds or circumvents Rate Limits; (b) shares or exposes API Credentials; (c) fails to display the required Attribution; (d) transmits prohibited categories of data or unlawful content; (e) engages in fraudulent, abusive, or malicious activity; or (f) is the subject of a legal order, sanctions designation, or credible allegation of unlawful conduct.
The Provider shall, where reasonably practicable and lawful, endeavor to inform the Developer of the suspension and the general reason for it, but is not obliged to give advance notice, to provide evidence of the misuse, or to disclose information that may compromise security or investigations.
Suspension may continue for as long as the Provider considers reasonably necessary to investigate, address, or resolve the issue. The Provider may reinstate access in whole or in part, subject to such conditions as it considers appropriate, including remediation by the Developer, but has no obligation to do so.
During any suspension, the Developer shall remain bound by these Terms and shall not attempt to access the API through other Developer Accounts, API Credentials, or any other means. Any such attempt constitutes a material breach of these Terms.
Suspension is without prejudice to the Provider's other rights and remedies, including termination, injunctive relief, and recovery of any losses. The Provider shall have no liability to the Developer or any End User for any suspension made under this section.
The Developer shall be responsible for informing End Users of any resulting interruption of the Application and for implementing measures to mitigate any impact on them.
Term, Termination, and Effects of Termination
These Terms commence on the Effective Date or, if earlier, the date on which the Developer first accepts them in accordance with the section governing acceptance, and continue until terminated in accordance with this section (the "Term").
The Developer may terminate these Terms at any time, for any reason or no reason, by ceasing all use of the API and closing the Developer Account or by notifying the Provider in writing at [Provider Contact Email].
The Provider may terminate these Terms, the Developer Account, and the Developer's access to the API, at any time, for any reason or no reason, with or without cause, and with or without notice. Where the Provider terminates for convenience and not for reasons related to the Developer's breach, misuse, security, or legal compliance, the Provider shall give the Developer not less than [Termination Notice Period] days' prior notice, except that where the termination results from the discontinuation of the API, the notice provisions of the section governing modification and deprecation shall apply.
Upon termination or expiry for any reason: (a) all licenses and rights granted to the Developer under these Terms immediately terminate; (b) the Developer shall immediately cease all access to and use of the API and the API Credentials; (c) the Developer shall remove the Attribution only where it is no longer using the API, and shall delete or destroy all API Content, Documentation, and API Credentials in its possession or control, except as required by Applicable Law; and (d) the Provider may disable the Developer Account and revoke all API Credentials.
The Developer shall, within [Post-Termination Period] days after termination, certify in writing, upon the Provider's request, that it has complied with its obligations regarding the deletion of API Content and the cessation of use.
The Provider may retain, delete, or dispose of any data associated with the Developer Account and the Developer's use of the API, including End-User Data, in accordance with its data retention practices, its privacy notice, and Applicable Law, and shall have no obligation to return or provide access to such data after termination, other than as required by Applicable Law or a data processing agreement between the Parties.
Termination or expiry shall not affect any rights, remedies, obligations, or liabilities of the Parties that accrued before termination. The provisions that by their nature are intended to survive termination shall survive, including the sections on restrictions, intellectual property rights, disclaimer of warranties, exclusion of liability, indemnification, governing law and dispute resolution, and general provisions, together with this section.
No compensation, refund, or damages shall be payable by the Provider to the Developer by reason of any termination or suspension in accordance with these Terms.
Amendments to These Terms
The Provider may amend, modify, supplement, or replace these Terms, the Documentation, and any Supplemental Policy at any time and in its sole discretion, including to reflect changes to the API, to Applicable Law, or to its business practices, and including by introducing fees or paid plans for the API or any part of it.
The Provider shall publish the amended Terms at [URL of Terms] and update the "Last Updated" date, and may additionally notify the Developer by email to the address associated with the Developer Account or by a notice through the developer portal or the API. Unless a different period is stated in the amended Terms or required by Applicable Law, amendments take effect [Amendment Notice Period] days after publication or notification, provided that amendments that the Provider reasonably considers necessary for legal, security, or regulatory reasons, or that impose no additional material obligations on the Developer, may take effect immediately.
Where an amendment introduces fees for access to or use of the API, the Provider shall give the Developer not less than 30 days' prior notice, and the Developer's continued use of the API after the effective date shall be subject to the applicable fees and terms.
The Developer's continued access to or use of the API after the effective date of an amendment constitutes the Developer's acceptance of the amended Terms. If the Developer does not agree to an amendment, the Developer must stop using the API and may terminate these Terms in accordance with the section governing termination.
It is the Developer's responsibility to review these Terms periodically. The Provider shall not be obliged to individually notify the Developer of every amendment where the amendment has been published as set out in these Terms.
No amendment shall apply retroactively to any dispute that arose before the effective date of the amendment, except where the amendment is made to comply with Applicable Law.
No variation to these Terms proposed by the Developer shall be effective unless set out in a written instrument signed by an authorized representative of the Provider.
Governing Law and Dispute Resolution
These Terms, and any dispute, claim, or controversy arising out of or in connection with them, including their formation, existence, validity, interpretation, performance, breach, or termination, and any non-contractual obligations arising from them (a "Dispute"), shall be governed by and construed in accordance with the laws of [Governing Law Jurisdiction], without regard to its conflict-of-laws rules.
The Parties shall first attempt in good faith to resolve any Dispute informally. The Developer shall give the Provider written notice of the Dispute, describing in reasonable detail its nature and the relief sought, addressed to [Provider Notice Address], and the Parties shall seek to resolve the Dispute within [Informal Resolution Period] days after receipt of the notice.
If the Dispute is not resolved within that period, the Dispute shall be finally resolved by [binding arbitration administered by [Arbitration Institution] in accordance with its rules in force at the time / the competent courts of [Court Jurisdiction]], as determined by the Provider and notified to the Developer. Where arbitration applies, the seat of arbitration shall be [Seat of Arbitration], the language of the proceedings shall be English, and the tribunal shall consist of [Number of Arbitrators] arbitrator(s).
To the fullest extent permitted by Applicable Law, the Developer agrees that any Dispute shall be brought and resolved solely on an individual basis, and not as a plaintiff or class member in any purported class, collective, consolidated, or representative proceeding.
Notwithstanding the foregoing, the Provider may at any time seek injunctive or other equitable or interim relief in any court of competent jurisdiction to protect or enforce its intellectual property rights, the confidentiality or security of the API, or its rights under the sections governing restrictions and suspension, without first complying with the informal resolution procedure.
Each Party shall bear its own costs in connection with any Dispute, except that the tribunal or court may award costs to the Provider where the Developer is found to be in breach of these Terms, to the extent permitted by Applicable Law.
Any claim by the Developer must be brought within the period stated in the section on exclusion of liability.
General Provisions
Assignment: The Developer may not assign, transfer, delegate, or subcontract any of its rights or obligations under these Terms without the prior written consent of the Provider, and any attempt to do so is void. The Provider may assign or transfer these Terms, in whole or in part, to any affiliate or to any successor to all or substantially all of its business or assets to which these Terms relate, without notice to or consent of the Developer.
Relationship of the Parties: The Parties are independent contractors. Nothing in these Terms creates any partnership, joint venture, agency, franchise, fiduciary, or employment relationship between the Parties, and neither Party has authority to bind the other.
Severability: If any provision of these Terms is held to be invalid, illegal, or unenforceable, that provision shall be modified to the minimum extent necessary to make it enforceable or, if that is not possible, severed, and the remaining provisions shall continue in full force and effect.
Waiver: No failure or delay by the Provider in exercising any right or remedy under these Terms constitutes a waiver of that right or remedy, and no single or partial exercise precludes any further exercise. A waiver is effective only if made in writing and signed by the Provider.
Force Majeure: The Provider shall not be liable for any failure or delay in performance resulting from causes beyond its reasonable control, including acts of God, natural disasters, war, terrorism, civil unrest, labor disputes, epidemics, government action, failures or delays of utilities, telecommunications, hosting, or cloud providers, power outages, cyberattacks, or denial-of-service attacks.
Notices: The Provider may give notice to the Developer by email to the address associated with the Developer Account, by posting on its website or developer portal, or through the API. The Developer shall give notice to the Provider in writing at [Provider Notice Address] with a copy to [Provider Contact Email]. Notices are deemed received 24 hours after dispatch by email or publication, or on delivery by courier.
Third-Party Beneficiaries: The Provider Parties and Indemnified Parties are intended third-party beneficiaries of the sections relating to disclaimers, exclusion of liability, and indemnification. Otherwise, no person other than the Parties has any right to enforce these Terms.
Entire Agreement and Language: These Terms, together with the Documentation and Supplemental Policies, constitute the entire agreement between the Parties regarding the API and supersede all prior agreements and understandings relating to it. These Terms are made in English, and any translation is provided for convenience only, with the English version prevailing in the event of conflict.
Electronic Execution: The Developer agrees that these Terms may be accepted electronically and that electronic acceptance, including by clicking to accept or by using the API, constitutes a valid and binding signature and agreement, and that no handwritten signature is required.
These Terms are issued by the Provider and accepted by the Developer by electronic acceptance as described above. Where the Developer is required or requested to provide confirmation of acceptance in writing, the details below shall be completed.
Provider: [Provider Legal Name]
Registered Address: [Provider Address]
Registration Number: [Registration Number]
Contact Email: [Provider Contact Email]
Authorized Signatory Name: [Provider Signatory Name]
Title: [Provider Signatory Title]
Signature: [Signature]
Date: [Date]
Developer: [Developer Legal Name or Full Name]
Entity Type and Jurisdiction (if applicable): [Developer Entity Type and Jurisdiction]
Address: [Developer Address]
Developer Account Identifier: [Developer Account ID]
Contact Email: [Developer Contact Email]
Application Name(s) and URL(s): [Application Details]
Authorized Signatory Name: [Developer Signatory Name]
Title: [Developer Signatory Title]
Signature: [Signature]
Date: [Date]
By signing above, or by registering for or using the API, the Developer confirms that it has read, understood, and agreed to be bound by these Terms.