> For the complete documentation index, see [llms.txt](https://docs.humdata.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humdata.org/about/hdx-terms-of-service/hapi-terms-of-service.md). # HAPI Terms of Service By using the HDX HAPI, you acknowledge that you have read, understood, and agreed to these terms of service. #### **Introduction** Welcome to the HDX Humanitarian API (HDX HAPI), a digital service provided by the Centre for Humanitarian Data. HDX HAPI is designed to disseminate key humanitarian datasets in a standardized and programmatically accessible format, specifically tailored for countries with active humanitarian response plans. #### **Acceptance of Terms** By accessing or utilizing HDX HAPI, you, the user, agree to comply with and be legally bound by these terms and conditions in full. Please read these terms carefully before using the API. If you disagree with any part of the terms, you must not use this service. #### **Usage Limitations** To ensure equitable access and maintain optimal performance for all users, the API imposes a restriction on the maximum number of entries retrievable per API call, capped at 10,000 entries. #### **Rate Limiting** We regulate the frequency of API calls to prevent overloading our systems and ensure reliable service for all users. Users are kindly requested to moderate their rate of requests to 1 per second. Further details on rate limiting practices will be provided upon request. #### **User Conduct** Users are prohibited from interfering with or disrupting the APIs, as well as any servers or networks connected to the APIs. Such interference includes actions that compromise the integrity, performance, or reliability of the service. #### **Data Logging and Analysis** The Office for the Coordination of Humanitarian Affairs (OCHA) is committed to continuously improving the HAPI service. As part of this effort, OCHA may log API calls and analyze usage patterns. Users are required to include the ‘app identifier’ parameters in their API requests to facilitate tracking and analysis for statistical and performance evaluation purposes. OCHA also uses third-party analytics services, including Google Analytics, Mixpanel and Hotjar. OCHA does not send identifying information (including names, usernames, or email addresses) to Google Analytics, Mixpanel or Hotjar. Use and retention of the data collected from the HDX platform is governed by these services’ respective Terms of Use. #### **Disclaimer** The data and information available through HDX HAPI do not represent the opinions of OCHA or the United Nations, nor do they imply any endorsement. This extends to opinions regarding the legal status of any country, territory, city, or area, including its authorities and the delineation of its frontiers or boundaries. #### **Contact Information** Should you have any inquiries or require further assistance, please do not hesitate to contact . --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.humdata.org/about/hdx-terms-of-service/hapi-terms-of-service.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.