For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
LoginGet a Demo
DocumentationAPI Reference
DocumentationAPI Reference
  • Start here
    • Welcome to HelloData API
    • Authentication
    • Pricing
    • Changelog
  • Concepts
    • Rate Limits
    • Respecting Rate Limits
    • Common Error Codes
    • Common Calculations
    • Ingestion Timeline
    • Deprecations
  • Examples
    • Property Search
    • Property Details & History
    • Identify Comparables
    • Price Recommendations
    • Property ID Changes
    • Dataset Export
  • Support
    • Contact Us
LogoLogo
LoginGet a Demo
On this page
  • Deprecation Cycle
Concepts

Deprecations

Improvements sometimes require changes
Was this page helpful?
Previous

Property Search

Find the properties you want to know everything about
Next
Built with

Deprecation Cycle

Our API is constantly evolving to provide the best data possible. We strive to make changes that improve the quality and usability of our data, but sometimes this means deprecating old features or endpoints. We follow a deprecation cycle to give you time to adjust to these changes. When we deprecate a feature, we will mark it as deprecated in the documentation and provide information on the recommended alternative. The typical deprecation cycle is as follows:

  1. Announcement: We will announce the deprecation in the changelog and provide information on the replacement or alternative.
  2. Deprecation: The feature will be marked as deprecated in the documentation.
  3. End of Life: About 3 months after the deprecation, the feature will be removed from the API. This can be a request parameter, response field, or entire endpoint.

We understand that changes can be disruptive, and we aim to make the transition as smooth as possible. If you have any questions or concerns about a deprecation, please reach out to us at support@hellodata.ai.