Salesforce Enrichment API — Apex Callout, Flow or Middleware

We have no AppExchange listing, no managed package, and no Salesforce-native app. If you came here to click Install, stop reading and go look at a vendor who has one. That is a real reason to pick someone else and we would rather you find out in the first paragraph than after a sales call.

What we have is an HTTP API that Salesforce can call three different ways. All three work. None of them involve a package upgrade breaking your sandbox.

This is the path for anything bulk or asynchronous, which is most of it.

public class RichApiEnrich implements Queueable, Database.AllowsCallouts {
    private List<Id> leadIds;
    public RichApiEnrich(List<Id> ids) { this.leadIds = ids; }

    public void execute(QueueableContext ctx) {
        List<Lead> toUpdate = new List<Lead>();
        for (Lead l : [SELECT Id, Name, Website FROM Lead WHERE Id IN :leadIds]) {
            HttpRequest req = new HttpRequest();
            req.setEndpoint('callout:RichAPI/api/v1/email_finder');
            req.setMethod('POST');
            req.setHeader('Content-Type', 'application/json');
            req.setBody(JSON.serialize(new Map<String, Object>{
                'full_name' => l.Name, 'company_domain' => l.Website }));
            HttpResponse res = new Http().send(req);
            Map<String, Object> body =
                (Map<String, Object>) JSON.deserializeUntyped(res.getBody());
            if (body.get('success') == true) {
                Map<String, Object> d = (Map<String, Object>) body.get('data');
                toUpdate.add(new Lead(Id = l.Id, Email = (String) d.get('email')));
            }
        }
        if (!toUpdate.isEmpty()) update toUpdate;
    }
}

Two Salesforce constraints shape this and you cannot design around them:

• No callouts after DML in the same transaction. Enrich, collect, then update once at the end. The loop above does that on purpose.
• Callouts per transaction are capped. Chunk the list and chain Queueables, or use Batch Apex with a small scope size. A list view button that tries to enrich a thousand leads synchronously will fail, and it will fail in a way that looks like our API broke.

Check body.get('success') and not the status code. A waterfall miss returns 200 with "success": false and "billed": false. If you branch on res.getStatusCode() == 200 you will write blank emails onto good leads.

If you do not want Apex in your org at all, put n8n or Make in the middle. New Lead fires a webhook, the middleware calls us, and its Salesforce node writes the record back. You trade a deployment for a subscription and a second place where things can break.

No app, no field mapping, no sync, no sending, no prospecting UI, no SCIM. We return JSON. You own the object model, and honestly you should. Nobody's managed package has ever guessed your custom fields correctly.

Related: company enrichment API, email verifier API, HubSpot for the other CRM with the same answer, verify before sequence push, and the full integrations index.

100 free credits, no card. Build the Named Credential and run one Queueable against ten leads before you commit to anything.