# API terms of use > The terms for using the Huispedia Data Intelligence API, with Annex A (contract endpoints) and Annex B (fair use). Source: https://huispedia.dev/en/voorwaarden/ **Last updated: 28 October 2026** :::note This is a translation. The [Dutch text on huispedia.nl](https://huispedia.nl/api-voorwaarden) is binding. ::: These terms apply to every use of the Huispedia API through [huispedia.dev](https://huispedia.dev), in addition to the [General Terms of Huispedia](https://huispedia.nl/algemene-voorwaarden). How Huispedia handles personal data is set out in the [privacy policy](https://huispedia.nl/privacybeleid). ## 1. Definitions **1.1** **API:** the Huispedia API that Housepedia B.V. (Chamber of Commerce 71325824, Keizersgracht 264, 1016 EV Amsterdam) offers through huispedia.dev. **1.2** **Customer:** the natural person, legal entity or business that holds an API account. A **Business Customer** acts in the course of a trade or profession. A **Consumer** is a Customer who does not. **1.3** **Output:** all data, valuations, scores and other results the API returns. **1.4** **End Customer:** a customer of the Customer to whom the Customer shows Output as part of its own services. **1.5** **Credits:** the unit for paid calls. **Plan credits** belong to a monthly plan. **Extra credits** are bought separately or through auto top-up. **1.6** **Contract endpoints:** Home value+, Comparable homes, Transactions and any endpoint Huispedia later designates as such. Annex A applies to them. **1.7** **Transaction data:** purchase prices and transaction dates of individual homes, whether they come from the Kadaster (Land Registry) or from agents and users connected to Huispedia. **1.8** **Data Sources:** parties Huispedia obtains data from, such as the Kadaster, CBS, the operators of the BAG and agents and users connected to Huispedia. ## 2. Applicability and order of precedence **2.1** These API terms supplement the General Terms of Huispedia for every use of the API. **2.2** In case of conflict, this order applies: (a) a signed agreement, (b) Annex A, (c) these API terms and Annex B, (d) the General Terms. **2.3** Purchasing or other terms of the Customer do not apply. ## 3. Account and API keys **3.1** At sign-up the Customer states whether it is a Business Customer or a Consumer. A Business Customer provides a valid Chamber of Commerce (KvK) number or, as a foreign business, an equivalent trade register number and VAT number. Huispedia may check these details and refuse or end an account if they are incorrect. Anyone who signs up as a Consumer but acts in the course of a trade or profession counts as a Business Customer. Contract endpoints are only available to Business Customers (Annex A). **3.2** The Customer keeps API keys secret. Keys do not belong in public code, apps or End Customers' browsers. **3.3** The Customer is responsible for all calls made with its keys, including misuse by third parties, until the Customer informs Huispedia of that misuse. **3.4** The Customer reports misuse or a leaked key immediately to [support@huispedia.nl](mailto:support@huispedia.nl). Huispedia may then revoke the key. ## 4. Licence **4.1** For the term of the agreement, Huispedia grants the Customer a limited, non-exclusive, non-transferable and non-sublicensable right to use the API and the Output under these terms. **4.2** For a Business Customer, the right applies only to the legal entity with the KvK number of the account; group companies need an account of their own. For a Consumer, the right applies only to them personally. **4.3** All rights not expressly granted remain with Huispedia and its Data Sources. ## 5. Permitted use of Output **5.1** The Customer may use Output in its own software, dashboards, CRM systems and customer portals. **5.2** The Customer may show Output per property to End Customers as part of its own services, for example in an advisory report. **5.3** The Customer may store (cache) Output for up to 30 days, unless Annex A prescribes a shorter period. Output that is part of a file or report about one property may be kept for as long as that file runs, but the Customer does not use it to build a database. **5.4** The Customer credits Huispedia as the source wherever Output is visible. Where the API or the catalogue names a Data Source (such as CBS or Kadaster), the Customer credits that source too. ## 6. Not permitted The Customer will not: - resell or sublicense Output, or make it available to third parties as raw data; - use Output to build or supplement its own database, dataset or data service; - use Output for a product that competes with Huispedia, or to train, test or improve AI models; - query the API systematically to collect a large part of the housing stock (scraping); - pass on calls for parties without a contract of their own, for example through a public portal or proxy; - get around limits, for example with several accounts or keys; - use Output for direct marketing (such as unsolicited mail or telemarketing) or for profiling people; - pose as Huispedia or a Data Source, or use their name or logo beyond the required source credit; - probe or decompile the API or get around its security. ## 7. Credits and plans **7.1** Only successful calls cost credits. A call is successful when the API returns a result (HTTP 2xx). Errors and calls without a result cost nothing. **7.2** The number of credits per endpoint is listed in the [catalogue](https://huispedia.dev/en/docs/catalogue/) on huispedia.dev. Huispedia may change this with 30 days' notice by email. **7.3** Plan credits are added at the start of each plan month and expire at the end of that month. They do not roll over. **7.4** Extra credits, bought separately or through auto top-up, are valid for 12 months from the date of purchase. They expire earlier if the account ends. **7.5** Calls are charged to plan credits first and then to extra credits, oldest first. The dashboard shows the balance and expiry date of each credit pack. **7.6** Plans renew automatically every month. The Customer can cancel at any time; the cancellation takes effect at the end of the current month. **7.7** Credits are never refunded, also not when they expire or the account ends. **7.8** Huispedia may index its prices every year on 1 January by the CPI (all households) of CBS. ## 8. Auto top-up **8.1** Auto top-up is off by default. The Customer switches it on and chooses a threshold, an amount per top-up and a monthly maximum. **8.2** By switching it on, the Customer authorises Huispedia to charge the saved payment method through the payment provider whenever the balance drops below the threshold, up to the chosen monthly maximum. **8.3** After every top-up the Customer receives a receipt by email. **8.4** The Customer can switch auto top-up off at any time in the dashboard. **8.5** If a payment fails, Huispedia may block paid calls until the balance is positive again. ## 9. Payment **9.1** Prices for Business Customers are exclusive of VAT. Prices for Consumers are inclusive of VAT. Payment runs through Huispedia's payment provider. **9.2** For Enterprise customers paying by invoice, the payment term of article 14.3 of the General Terms applies (14 days). **9.3** The API supplies digital content: with each call the Customer receives data right away. A Consumer loses the right of withdrawal once delivery has started, if they expressly agreed beforehand to immediate delivery and stated that they thereby lose their right of withdrawal. Delivery starts as soon as the credits are added to the account. Huispedia confirms this by email after the order. If the supply nevertheless counts as a service, a Consumer who withdraws pays pro rata for what they have already used. ## 10. Free plan **10.1** The Free plan is meant for testing and developing with the API. The Customer does not use it in production towards End Customers. Wherever Output is visible, the Customer states "Data: Huispedia". **10.2** Lower limits apply to the Free plan. Huispedia may change or end the Free plan at any time. **10.3** Contract endpoints are not available on the Free plan. ## 11. Availability and changes **11.1** Huispedia does its best to keep the API available but gives no guarantee of availability. An SLA applies only if agreed in writing (Enterprise). **11.2** Huispedia announces changes that break existing integrations at least 60 days in advance by email and in the [changelog](https://huispedia.dev/en/docs/changelog/). In case of an acute security or legal risk, this can be sooner. **11.3** Huispedia may change or stop endpoints if a Data Source limits or ends its supply. If an endpoint stops for that reason, the Customer deletes the Output of that endpoint within 30 days at Huispedia's request. ## 12. Indicative nature **12.1** Valuations and other Output are model-based and indicative (articles 3.5 and 11 of the General Terms). They are not an appraisal. **12.2** The Customer does not present Output to End Customers as an appraisal and is itself responsible for its advice and decisions. The Customer states in its own terms, or in the report or view in which it shows Output, that the Output is indicative and not an appraisal. ## 13. Suspension **13.1** Huispedia may limit or suspend access in case of a breach of these terms, overdue payment, a risk to the stability or security of the API, or when a Data Source demands it. **13.2** If improper use is suspected, Huispedia first gets in touch, unless immediate action is needed. ## 14. Liability and indemnity **14.1** Huispedia provides the API and the Output as they are ("as is"). Huispedia does not warrant the accuracy, completeness or currency of Output or of data from Data Sources. **14.2** Huispedia is not liable for (a) indirect and consequential damage, (b) lost profit, revenue or savings, (c) loss of or damage to data, (d) reputational damage, (e) damage from decisions or advice based on Output, (f) damage from inaccurate or discontinued data from Data Sources, and (g) claims of End Customers. **14.3** To the extent Huispedia is liable after all, its total liability towards the Customer, on whatever ground, is limited to the amount (excluding VAT) the Customer paid Huispedia for the API in the 12 months before the first event causing the damage, with a maximum of € 500 per calendar year. Related events count as one event. This article prevails over article 12.2 of the General Terms. **14.4** A right to compensation only arises if the Customer reports the damage in writing within 30 days of discovering it. Claims lapse 12 months after the event causing the damage. **14.5** The Customer indemnifies Huispedia against claims of third parties, including Data Sources, End Customers and data subjects under the GDPR, arising from (a) use in breach of these terms or the law, (b) use of Output in the Customer's services, or (c) calls made with the Customer's API keys. This includes fines and compensation a Data Source imposes on Huispedia and reasonable legal costs. **14.6** If the Customer is a Consumer, paragraphs 1 to 4 do not apply and paragraph 5 applies only to use in breach of these terms or the law. Huispedia's liability towards a Consumer is governed by article 12 of the General Terms. A Consumer's statutory rights remain unaffected. **14.7** The limitations in this article do not apply in case of intent or deliberate recklessness of Huispedia's management. ## 15. Privacy and logs **15.1** Huispedia processes account data and request logs (such as key, IP address, endpoint, requested address and time) as controller for security, billing, fair use and reporting to Data Sources. Huispedia keeps request logs for 12 months, logs of Contract endpoints until 2 years after the end of the calendar year, and billing data for 7 years because of the statutory tax retention period. After that, Huispedia deletes or anonymises this data. **15.2** Output may contain personal data, such as an address with a purchase price. For its own use of it, the Customer is an independent controller and complies with the GDPR. **15.3** If Huispedia processes personal data on the Customer's behalf, the parties sign a data processing agreement on request. ## 16. Intellectual property **16.1** All rights in the API, the models and the Output, including database rights, remain with Huispedia and its Data Sources. **16.2** Huispedia may use the Customer's feedback freely. ## 17. Termination **17.1** When the agreement or the account ends, the right of use ends. The Customer stops using the API immediately and deletes all stored Output within 30 days, unless Annex A prescribes a shorter period. It deletes the Output from backups as soon as they are overwritten in the normal cycle. Output in reports delivered to End Customers before termination, or that the Customer must keep by law, may remain, but is not used further. On request, the Customer confirms the deletion in writing. **17.2** Articles 6, 12, 14, 15, 16 and 19 and Annex A (in particular A4, A7, A8 and A10) survive termination. ## 18. Changes to these terms **18.1** Huispedia announces changes at least 30 days in advance by email and in the dashboard. **18.2** Changes that are required by law, that a Data Source demands, or that do not materially disadvantage the Customer take effect without the Customer being able to cancel because of them. **18.3** If a change materially disadvantages the Customer, it may cancel the agreement as of the effective date. Cancelling gives no right to a refund of credits, unless the law requires one. **18.4** Use after the effective date counts as acceptance. ## 19. Law and disputes Dutch law applies. Disputes go to the competent court as set out in article 19 of the General Terms: for Business Customers the court in Amsterdam (article 19.2), for Consumers under article 19.1. ## Annex A: Contract endpoints **A1. Access.** Contract endpoints are only available after a signed agreement. Access is limited to Business Customers that Huispedia has verified through the KvK and, where applicable, the relevant professional register, and that fall into a category the Data Source concerned has allowed in writing. For Kadaster transaction data, these are currently estate agents, appraisers and mortgage advisers. The agreement states the specific purpose of use. **A2. Purpose limitation.** The Customer requests Contract endpoints only to value one specific property in an ongoing assignment. Per valuation, the Customer receives at most 5 reference transactions plus the last known purchase price of the property itself. The Customer does not use this data for other properties or purposes. **A3. Restricted display.** The Customer shows Transaction data only in an environment behind a login, or in a report for the client of that valuation. Not on public websites, in property listings, in marketing or in public portals. **A4. Storage.** The Customer keeps Transaction data only in the file or report of the valuation concerned, and no longer than a statutory or professional retention duty requires. The Customer does not build its own file of transactions and does not use them to train models. **A5. Personal data.** Transaction data may be personal data. The Customer does not use it for direct marketing (including direct mail and telemarketing) or profiling, and does not provide it to third parties other than the client of the valuation. **A6. Source credit.** The API returns the source of each transaction. Wherever Transaction data is visible, the Customer shows that source, for Kadaster data as "Bron: Kadaster" with the year of the data. The Customer does not use the Kadaster's name and logo in any other way and does not give the impression of acting on the Kadaster's behalf. **A7. Logging and audit.** Huispedia records every transaction supplied per Customer. The Customer cooperates with audits by Huispedia, the Kadaster or a chartered accountant and gives insight into its use within 10 working days on request. **A8. Destruction.** When the agreement ends, or when supply by a Data Source ends, the Customer destroys all Transaction data within 5 working days and confirms this in writing. Exception: completed reports under a statutory retention duty, which the Customer does not use further. **A9. Change by a Data Source.** If a Data Source limits, suspends or ends its supply, Huispedia may change or stop the Contract endpoints immediately. The Customer then stops using them immediately. Huispedia refunds prepaid contract fees for the remaining period pro rata. **A10. Penalty and indemnity.** For each breach of A2 to A8, the Customer owes an immediately payable penalty of the amount stated in the signed agreement, in addition to compensation of all damage. The Customer fully indemnifies Huispedia against claims and compensation of the Kadaster and other Data Sources resulting from its breach. **A11. Takeover.** The Customer reports a merger, takeover or demerger in advance. The right of use does not pass automatically to new group companies. **A12. Publicity.** The Customer does not publish about the Transaction data or its origin without consulting Huispedia first. ## Annex B: Fair use policy In one sentence: use the API as much as you like for your own processes and your own customers, as long as you do not resell the data, do not systematically collect the housing stock and do not overload the platform. | Plan | Requests per second | Daily signal value | Contract endpoints | | --- | --- | --- | --- | | Free | 1 | 500 calls | No | | Standard (Starter, Growth, Scale, Pro) | 6 | 20,000 calls, sustained | No | | Contract / Enterprise | Per agreement | Per agreement | Yes, within Annex A | **Permitted** - Intensive business use by one organisation, with several users and departments within the same legal entity. - Integration into your own software, CRM and customer portals (behind a login). - Batch processing for your own ongoing files, with caching up to 30 days. **Not permitted** - Reselling raw data or making it available to third parties outside your own organisation. - Using the API as a proxy or mirror for another data service. - Automatically passing on calls for non-customers, such as a public portal without a white-label agreement. - Collecting large parts of the housing stock, for example a whole municipality or the whole country in a short time. - Using several accounts or keys to get around limits. **Enforcement** 1. Huispedia monitors usage patterns, such as sustained peaks above the signal value and requests that systematically cover an area. 2. If misuse is suspected, Huispedia first gets in touch and looks for a solution together, such as an Enterprise or white-label contract. 3. In case of an acute risk to the platform, Huispedia may throttle immediately (HTTP 429). 4. In case of deliberate or repeated misuse after a warning, Huispedia may suspend or end access. Huispedia may change this policy with 30 days' notice by email.