CRM account logos
Keep account and lead records recognizable without another SDK.
A small, accountless image primitive for product interfaces, directories, and agent-built UIs. No signup, no API key, and no ReplyNodes credits. Pass a domain. Get a URL that works in an image tag.
https://img.replynodes.com/stripe.com01 / Test the contract
Use the live endpoint with a domain you recognize. The preview reflects the real response; no local artwork is used as a success stand-in.
Live request
Quick examples
https://img.replynodes.com/stripe.comEndpoint response
stripe.com
Loading the image endpoint for stripe.com.
Drop-in code
<img src="https://img.replynodes.com/stripe.com" alt="Stripe logo" /><img
src={`https://img.replynodes.com/${domain}`}
alt={`${company} logo`}
/>Real endpoint proof
Every tile requests the public image endpoint. Results are shown in grayscale; unavailable responses stay neutral.
02 / Use the primitive
No SDK, authentication layer, or ReplyNodes credits for the public Company Logo API. Keep the contract visible in your code and choose the fallback that fits your product.
A public domain such as stripe.com.
The endpoint returns the best available brand image.
Use the result anywhere an img tag works.
Keep a neutral state when a response is unavailable.
https://img.replynodes.com/{domain}03 / Fit the surface
Use the domain you already have to add a quiet brand signal to the surfaces people scan every day.
Keep account and lead records recognizable without another SDK.
Give every team and customer workspace a familiar visual anchor.
Add a useful brand signal to search results and listings.
Pair company names with a logo as people find what they need.
Make a transaction list easier to scan at a glance.
Show the company behind a report, integration, or account.
Help candidates recognize employers in a dense results list.
Let agent-built UIs add a logo without shipping an SDK.
Keep generated documents and decks grounded in the company domain.
04 / Moving from Clearbit
The migration is intentionally narrow: replace a basic Clearbit domain lookup, then test the domains and fallback states your application relies on. Do not assume legacy query parameters or broader feature parity.
https://logo.clearbit.com/stripe.comhttps://img.replynodes.com/stripe.com05 / Brand Intelligence
The Logo API is the small public primitive. Brand Intelligence is a separate product surface for colors, fonts, style guides, company metadata, and richer brand assets where supported.
The Logo API remains accountless. For the broader ReplyNodes platform, create an account or log in.
06 / FAQ
A Company Logo API turns a public company domain into an image URL that you can use in a product, document, or interface.
Use https://img.replynodes.com/{domain}. For example, https://img.replynodes.com/stripe.com returns the image endpoint for Stripe's domain.
No. The public logo image endpoint does not require an API key.
No. You can use the public logo image endpoint without a ReplyNodes account.
No. Requests to the public logo image endpoint do not use ReplyNodes credits.
The endpoint uses deterministic fallback behavior. Depending on what is available, that can mean a logo, a favicon, or a neutral placeholder.
Yes. Use <img src="https://img.replynodes.com/stripe.com" alt="Stripe logo" /> directly in your HTML.
It supports the same basic domain-to-image URL integration pattern as a Clearbit Logo API lookup. Do not assume legacy Clearbit parameters or broader feature parity are supported.
Logo refresh and correction tooling is not yet self-service. If a result needs attention, use a fallback in your interface while the source is reviewed.
This page does not publish a usage-limit or fair-use promise. Check the current endpoint behavior for the application you are building and avoid assuming unlimited usage.
Try the public image URL before you add anything else.