---
title: "Create Find Contact Data Job"
method: POST
path: "/v1/contacts/find-contact-data-jobs"
tags: ["Contacts", "Enrichment", "v1"]
---

# Create Find Contact Data Job

`POST /v1/contacts/find-contact-data-jobs`

Trigger an asynchronous job to enrich the given contacts with email and phone data. Accepts either explicit `contact_ids` or a `list_id` to target an entire list. The job runs in the background; poll the status endpoint to check progress.
Credit Note: Credits are consumed as contacts are enriched.

:::info
Requires the `contacts:read` OAuth2 scope.
:::

## Query parameters

- `account_id` string, required

## Request body

- object
  - `data` object, required
    - `type` string

## Response `202`

Job accepted and started

- object
  - `data` FindContactDataJobV1, required
    - `type` string, required
    - `id` string, required — Unique job identifier
    - `attributes` object, required
      - `status` 'running' | 'completed' | 'failed', required — Current status of the job
      - `configuration` object — Echoed request configuration. Present once the job has started. Reflects the caller's input shape: either `contact_ids` or `list_id`.
        - `contact_ids` string[] — Contact IDs submitted for enrichment. Mutually exclusive with `list_id`.
        - `list_id` string — List ID targeted for enrichment. Mutually exclusive with `contact_ids`.
      - `credits` object — Credit consumption details
        - `estimated` integer — Credits estimated at job creation
        - `consumed` integer — Credits consumed so far
      - `summary` object — Record processing summary
        - `total` integer — Total records to process
        - `succeeded` integer — Records enriched successfully
        - `failed` integer — Records that failed enrichment
      - `errors` object[] — Present only when status is `failed`
        - `code` string, required — Machine-readable error code
        - `title` string, required — Human-readable error description
      - `created_at` string, date-time, required — When the job was created
      - `completed_at` string, date-time, nullable — When the job completed (null while running)
  - `meta` object, required
    - `request_id` string, required — A unique identifier assigned to each API request for end-to-end traceability.

## Other responses

- `400` — Invalid request body envelope
- `401` — Unauthorized. The request was rejected because the credentials are missing, invalid, expired, or have been revoked. The client must re-authenticate before retrying. Clients can differentiate via the `code` value of the first item in `errors`.
- `403` — Forbidden. The credentials are valid but the caller is not authorized to perform the request — typically because the user lacks the required permission, the OAuth scope is insufficient, the subscription plan does not include the required entitlement, the `account_id` does not belong to the authenticated user, or the target list is read-only and its members cannot be modified. Clients can differentiate via the `code` value of the first item in `errors`.
- `422` — Unprocessable content — request body is well-formed but fails domain validation
- `429` — Too many requests. Either the per-second rate limit or the monthly quota configured for the API key / OAuth application has been exceeded. Clients can differentiate via the `code` value of the first item in `errors`.
- `500` — Internal server error

---

[API](https://skmtc.net/leadfeeder/apis/leadfeeder-public-api.md) · [All operations](https://skmtc.net/leadfeeder/apis/leadfeeder-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/leadfeeder/leadfeeder-public-api/versions/e494ac05e206/schema)