Enrichment API

Enrichment that fits your stack

Most enrichment tools were built for humans clicking through a UI. They return CSV exports, inconsistent field names, and no way to know where a value came from. When you are wiring people data into a CRM sync, a lead-routing workflow, or an AI agent, that model breaks immediately. Ploid's Enrichment API is built for programmatic use from the start: queue a batch job, poll for completion, and receive typed, schema-validated JSON with sources attached to every field.

Single-record enrichment is available through POST /v1/people/enrich when you need one profile on demand. For lists, imports, and anything that should not block your request thread, POST /v1/people/batch/enrich accepts thousands of people, runs them asynchronously, and lets you pull results page by page when the job finishes. Estimate cost before you commit, set a max spend cap, and choose exactly which fields you need — email, phone, GitHub, X, Instagram, TikTok, and more.

Schema-validated output you can trust downstream

The hardest part of integrating people data is not the HTTP call — it is handling whatever comes back. Missing keys, stringly-typed booleans, and “verified” flags with no explanation behind them force every consumer to defensively parse and guess. Ploid returns a consistent schema on every response. Field names do not change between records. Types are explicit. When a value is present, you also get the evidence that supports it: which source it came from and how confident the match is.

That matters when your scoring model, routing rules, or agent reasoning depends on the data being real. A rep can eyeball a bad email. An automation cannot. With sourced, schema-validated payloads, your downstream systems can enforce confidence thresholds, audit decisions, and fail safely instead of silently acting on garbage.

Bulk jobs without babysitting

Conference leads. Trial signups. A CRM export that is 80% empty. Vendor onboarding lists. The use cases for bulk enrichment are endless, and they all share the same requirement: process a lot of rows without tying up your application or your team. Ploid batch jobs queue instantly, run in the background, and notify you via webhook when they complete. Poll job status and stream results with cursor-based pagination — no single giant response that times out at the gateway.

Because identity resolution happens inside the job, you are not just appending columns to whatever name string you had. Ploid matches each person across hundreds of sources, resolves duplicates, and enriches the correct profile. The row that said “Sarah Chen” with no company comes back as a complete record with title, employer, verified contact channels, and social profiles — or an explicit low-confidence signal when the match is ambiguous.

Built for agents and automations

AI agents and workflow tools need structured data, not HTML. The Enrichment API is the same people intelligence layer that powers the Ploid workspace, exposed as a primitive your code can call. Drop it into n8n, LangChain, a custom ETL pipeline, or your own backend — one API key, one schema, one evidence model whether you enrich one person or a million.

Webhooks fire on batch.completed so your pipeline can pick up results without polling. Scopes are granular — search, lookup, enrich, batch write — so you can issue keys with least privilege. And because Ploid is tech-agnostic by design, you are not locked into our UI or our storage. Send people in, get enriched JSON out, and write it wherever your system of record lives.

Start in the playground, ship in production

You do not need a sales call or a six-week integration project. Create an API key, open the Enrich playground, and run a single enrichment or queue a batch job with real payloads. Copy the request, paste it into your codebase, and you are live. The same endpoints, the same schema, the same sources — from your first test call to your billionth production enrichment.