> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bizzy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Enrich Contact

Queues an email and/or mobile phone enrichment for a contact. This endpoint always returns immediately with a `PENDING` job — poll [Enrichment Status](../enrichments/status) with the returned `enrichmentId` to get the result.

<Note>
  Enriching costs credits - see the [Credit usage section](../credits)
</Note>

## Request

#### Path

<ParamField path="companyId" type="string" required>
  Obfuscated companyId returned by the search endpoint.
</ParamField>

<ParamField path="contactId" type="string" required>
  ContactId is the unique identifier of the contact.
</ParamField>

#### Body

<ParamField body="enrichEmail" type="boolean" default="false">
  Enrich the contact with an email address, if available.
</ParamField>

<ParamField body="enrichMobilePhone" type="boolean" default="false">
  Enrich the contact with a mobile phone number, if available.
</ParamField>

<Note>
  At least one of `enrichEmail` or `enrichMobilePhone` must be `true`.
</Note>

## Response

Returns `202 Accepted` with a `Location` header pointing at `/enrichments/{enrichmentId}`.

<Note>
  When the enrichment resolves synchronously (nothing to queue) and a credit is charged, the response includes `X-Bizzy-Credits-Balance` and `X-Bizzy-Credits-Charged` headers — see [Credit usage](../credits).
</Note>

<ResponseField name="enrichmentId" type="string">
  Obfuscated id used to poll the [Enrichment Status](../enrichments/status) endpoint.
</ResponseField>

<ResponseField name="status" type="string">
  Always `PENDING` on creation.
</ResponseField>

<ResponseExample>
  ```json Response - 202 theme={null}
  {
      "enrichmentId": "8817263",
      "status": "PENDING"
  }
  ```
</ResponseExample>