---
title: "Trigger enrichment for a person"
method: POST
path: "/api/v1/people/{id}/enrich"
tags: ["People"]
---

# Trigger enrichment for a person

`POST /api/v1/people/{id}/enrich`

Use this endpoint to trigger Atlas' background enrichment for an existing person — the REST equivalent of **Sync profile** in the Atlas UI.

**This endpoint is asynchronous.** It returns **202 Accepted** as soon as the job is queued and does *not* wait for the enrichment to finish; enrichment can take from seconds to minutes. Poll `GET /api/v1/people/{id}` and read `enrichmentStatus` (`in_progress` → `completed` or `failed`) to find out when it is done, then re-read the person to see the new data. The list endpoint `GET /api/v1/people` does not return `enrichmentStatus`.

**Enrichment types** (optional `type` in the body):
- `contacts` (**default**) — looks up email addresses and phone numbers from the person's public LinkedIn profile and adds them as identities. Existing identities are never overwritten. Requires a **public** LinkedIn profile URL on the person.
- `full` — runs the complete CES profile sync: work experience, headline, and identities. Requires a LinkedIn URL **or** both a first and last name.

**Usage.** Both types count towards your agency's enrichment usage exactly as the equivalent actions in the Atlas UI do; this endpoint is not capped separately from the app. Automated loops can burn through enrichments quickly — enrich deliberately rather than on every sync pass.

**Re-triggering.** While a person's `enrichmentStatus` is `in_progress`, a second call is rejected with **422**. Wait for it to settle before calling again.

**Side effects.** Enrichment adds and merges identities and experiences on the person. Conflicting values are skipped, never overwritten, and adding an experience recalculates the person's headline.

## Path parameters

- `id` string, uuid, required — Atlas person ID

## Request body

- object
  - `type` 'full' | 'contacts' — Which enrichment to run. `contacts` (default) looks up email/phone from the LinkedIn profile; `full` runs the complete CES profile sync (experiences, headline, identities).

## Response `202`

Enrichment queued. Poll GET /api/v1/people/{id} for `enrichmentStatus`.

- object
  - `status` 'ok', required
  - `data` object, required
    - `personId` string, uuid, required — The person the enrichment was queued for
    - `type` 'full' | 'contacts', required — The enrichment that was queued
    - `enrichmentStatus` 'in_progress', required — Always `in_progress` — poll GET /api/v1/people/{id} for the outcome

## Other responses

- `401` — Unauthorized - missing or invalid API key
- `404` — Person not found
- `422` — Invalid `type`, enrichment already in progress, the person is missing the data enrichment needs (a public LinkedIn URL for `contacts`; a LinkedIn URL or first+last name for `full`), or the CES contact integration is not active for the token owner (`contacts` only).
- `429` — Too many requests - the caller has exceeded the per-agency rate limit for the tier this endpoint counts against (default per minute: 1200 read / 400 write / 60 upload). Inspect the `RateLimit-*` headers — returned on every response, not only on 429s — and back off until the window resets. See the "Rate limits" section of the introduction for details.
- `500` — Internal server error

## Changes

- **2026-09-15** `1131a0974b93` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/recruitwithatlas/apis/atlas-api/changes/api/v1/people/:id/enrich/post.md)

---

[API](https://skmtc.dev/recruitwithatlas/apis/atlas-api.md) · [All operations](https://skmtc.dev/recruitwithatlas/apis/atlas-api/llms.txt) · [OpenAPI document](https://skmtc.dev/recruitwithatlas/apis/atlas-api/revisions/bfc1118eeb5d?raw)