Skip to main content

Why does the New API Replace the Echobot API

We're replacing the legacy Echobot API with a new unified API that's simpler, faster, and more powerful.

A
Written by Anna-Maria Samuelsson
Updated today

We are introducing a new unified API that replaces the legacy Echobot API with a more modern solution that works better for you.
​

What's Changing?

The legacy Echobot API had its own authentication method, credit system, and data format. This made it complex to build and maintain integrations.

The new unified API simplifies everything:

  • One API key for company data, contact data, and IP enrichment operations

  • One credit system shared between the platform and API

  • Better performance with improved reliability and speed

  • New features like bulk requests and access to your custom fields, tags, and lists

What You Need to Do

Legacy Echobot API customers need to migrate to the new API:

  • Generate a new API key in your platform settings -> personal -> API Keys (legacy keys will not be migrated)

  • Update your integrations to use the new endpoints

  • Update your integration to handle the new response structure

You can find the new documentation here.
​
You'll have a transition period to make these changes.

Did this answer your question?