Clearbit API: What Is Retired, What Is Left, and How to Migrate

Clearbit published two different sunset dates for the same API on two of its own surfaces. The banner on clearbit.com/logo says the Logo API will be discontinued on 1 December 2025. A changelog entry dated 24 November 2025 says that after 8 December 2025 the public Logo API URL will no longer be available for use. Both pages were serving those sentences when we fetched them in August 2026, a week apart in claim and nine months stale in fact.

That contradiction is a fair introduction to the state of the Clearbit API generally. This page covers which endpoints are retired, which still answer, what the documentation situation actually is, and what to do if you are maintaining an integration that depends on any of it.

The four things people mean by the Clearbit API

The name covered a family of endpoints with quite different audiences.

Enrichment took a company domain or an email address and returned structured attributes: headcount, industry, location, technologies, funding, role and seniority. This was the commercial core and the reason most teams held a subscription.

Reveal took an IP address and returned the company likely behind it, which is a different product with its own integration ecosystem. It is covered separately in our page on Clearbit Reveal.

Autocomplete, sometimes called the name-to-domain API, resolved a company name into a domain and a logo. It was free, it was fast, and it ended up embedded in an enormous number of signup forms and internal tools as a convenience.

The Logo API returned a company's logo image from its domain. It was free, required no key for basic use, and became one of those quiet pieces of internet infrastructure that thousands of products depended on without anyone filing a ticket about it.

What is retired, and when

The Logo API is the one with published dates, and it is worth setting the record out in full because the versions disagree.

1. 13 Feb 2025Free products named

   A changelog entry announces that the free Clearbit Platform, Weekly Visitor Report, Clearbit Connect, TAM Calculator and free Slack integration will be discontinued on 30 April 2025, and states that the Logo API will sunset on 1 December 2025.

2. 10 Jun 2025Scope confirmed

   A further entry repeats the 1 December 2025 sunset and states the change affects all users, including those with active subscriptions.

3. 9 Sep 2025Autocomplete degraded first

   From this date the logo field in the Autocomplete API returns null, per the same entry.

4. 12 Nov 2025Planned outage

   A 24-hour outage is announced ahead of the full sunset.

5. 1 or 8 Dec 2025Sunset

   The product page banner says 1 December. The most recent changelog entry says the public URL will be unavailable after 8 December. Both are still published.

Two details in that sequence deserve more attention than the dates.

The first is the sentence stating the change affects all users, including those with active subscriptions. A paid contract did not buy an exemption, which is a useful reminder that a free endpoint inside a paid product is governed by the product's roadmap and not by your invoice.

The second is that the Autocomplete API kept working while its logo field started returning null in September 2025. That is the most dangerous shape a deprecation can take: an endpoint that keeps returning 200 with a structurally valid response and a field that has quietly gone empty. Nothing in a status-code check catches it, and a form that renders a logo simply stops rendering one.

What still answers

The enrichment surface has not been given a published end date on any Clearbit page we could read. clearbit.com/platform/enrichment still loads and still describes the product. There is no announcement retiring it, and there is also no way to buy it: across every Clearbit page still serving content, the only account link is a login for existing customers, and the one call to action on the enrichment page jumps to a lead form rather than to a checkout.

Absence of a sunset notice is weak evidence of a future. Clearbit has announced its retirements plainly when it made them, so the silence here is genuinely ambiguous rather than reassuring, and the wider context is that HubSpot acquired the company and moved the capability into its own credit-priced products. Our page on Clearbit enrichment covers where the commercial surface went.

The documentation

clearbit.com/docs returns a page with no documentation in it. What the server sends is a small React shell: a title, a noscript tag telling you to enable JavaScript, an empty root element and a bundle reference. There is no authentication wall in that response and no content either.

For a developer evaluating whether to build on a platform, that distinction barely matters. Documentation you cannot read from a plain request is documentation you cannot search, cannot link a colleague to a specific section of, and cannot rely on being archived. For an existing integrator, it means the reference you need is reachable in a browser and awkward everywhere else.

If you have an integration that depends on any of this

Auditing a Clearbit dependency

• ✕No: Grep for logo.clearbit.com. Any hit is calling a retired endpoint
• ✕No: Grep for autocomplete calls that read a logo field. It has returned null since September 2025
• ~Depends: List every enrichment call and what each returned field decides downstream
• ~Depends: Check whether any field routes leads, scores records or gates a workflow
• ✓Yes: Confirm your own account still authenticates, and export what you already hold
• ✓Yes: Replace null-tolerant rendering with an explicit fallback rather than an empty space

The general principle is worth stating on its own, because it outlives this vendor. A deprecation that changes a field's value rather than an endpoint's status code is invisible to every health check most teams run. Monitoring that asserts on HTTP 200 will report a green service for months while the data it returns hollows out. The check that catches this class asserts on the shape and the content of a response, not on whether it arrived.

For the logo case specifically, the vendor's own page names Logo.dev as an alternative, which is the rare case of a retirement notice pointing somewhere useful. That page also carries a second sentence worth reading carefully before you plan a migration: the Clearbit logo API is described as no longer available for new users, which is a different and earlier condition than being switched off. Products in that state keep serving existing traffic while quietly refusing new accounts, so an integration that has worked for years can look perfectly healthy right up to the point where you try to reproduce it in a new environment and discover you cannot sign up.

Why free endpoints go first

Every Clearbit surface with a published end date was a free one. The free platform, the Weekly Visitor Report, the TAM Calculator, the free Slack integration, Clearbit Connect and the Logo API were all announced for retirement, while the paid enrichment core has never been given a date. That ordering is not a coincidence and it generalises well beyond this vendor.

A free endpoint is a marketing asset. It exists to put the company's name in front of developers who might later buy something, and it is carried on the paid product's cost base. When ownership changes, the acquirer inherits the cost and not the original marketing rationale, so the free surfaces are the first line anyone looks at. The Logo API's own history illustrates the scale of what that decision touches: an endpoint requiring no key, embedded in thousands of products by developers who never signed anything and were therefore never anybody's customer to notify.

The practical version of this for your own architecture is a short rule. A dependency you did not pay for is a dependency nobody owes you notice about. That does not mean avoiding free endpoints, which would be silly. It means recording where you use one, and writing the fallback at the time you add it rather than at the time it breaks.

Choosing what to build on next

If you are replacing enrichment rather than logos, the field is well populated and the right answer usually follows your CRM rather than your data preferences. Our Clearbit alternatives roundup covers the category.

If what you actually need is contact addresses for people you have already identified, that is a different job and an enrichment API is the wrong shape for it. A waterfall runs providers in order, stops at the first confident result, and only pays the next stage for the rows the previous stage could not resolve. The stack we run is MillionVerifier brute-force first, then Prospeo, then Findymail, with no fourth paid stage, and the protocol for testing any provider against rows you already hold verified addresses for is in our guide to email finder tools.

Whatever you pick, the lesson from this particular wind-down is worth writing into the integration itself. Log which vendor answered each field, keep the raw response rather than only the parsed fields, and make the fallback path a real code path rather than a null flowing quietly into a template. That work costs an afternoon and it is the difference between a migration and an incident.

The short version

The Clearbit Logo API is retired, on a date the vendor published as both 1 and 8 December 2025 on two of its own live surfaces. The Autocomplete API's logo field has returned null since 9 September 2025, which is a deprecation no status-code monitor detects. The retirement was stated to affect all users including those with active subscriptions. The enrichment endpoints carry no published end date and no purchase path, with the only account link on the site being a login for existing customers. The documentation URL serves a client-rendered shell with no content in the response. If you maintain an integration, grep for the retired endpoints first, then audit which enrichment fields are load-bearing before the decision is made for you.

If you would rather see an outbound motion running on your own ICP without assembling a data stack first, start a free campaign and we will build the list, the copy and the sending infrastructure around it.

Pricing and features verified as of August 2026. Verify current terms with the vendor before relying on them.