Poll Batch Account Enrichment Job

GET

api

enrich

accounts

{job_id}

Poll Batch Account Enrichment Job

curl --request GET \
  --url https://api.openfunnel.dev/api/v1/enrich/accounts/{job_id} \
  --header 'X-API-Key: <x-api-key>'

{
  "job_id": "<string>",
  "status": "<string>",
  "progress": {},
  "result": [
    {
      "domain": "<string>",
      "status": "<string>",
      "account_id": 123,
      "name": "<string>",
      "is_new_account": false,
      "fields_updated": [
        "<string>"
      ]
    }
  ],
  "error_message": "<string>"
}

Headers

X-API-Key

string

required

Path Parameters

job_id

string

required

Response

Successful Response

Response from polling a batch account enrichment job.

job_id

string

required

Job ID

status

string

required

'pending', 'running', 'completed', or 'failed'

progress

Progress · object

Progress info: {total, completed, new_accounts, updated_accounts}

result

EnrichAccountBatchResult · object[] | null

Per-domain results - available when status is 'completed'

Show child attributes

error_message

string | null

Error details - present only when status is 'failed'

Deep EnrichEnd-to-end company qualification and people enrichment. 1. Creates or finds the account for the given domain. 2. Finds intent signals for the company. 3. Enriches the account with people - finds relevant team members and ICP qualifies them. Requires either `icp_id` or `target_icp_roles`. Runs in background - use `account_id` to get latest account status. Deep enrichment can take 15-30 minutes to find intent signals and people.

⌘I

Poll Batch Account Enrichment Job

curl --request GET \
  --url https://api.openfunnel.dev/api/v1/enrich/accounts/{job_id} \
  --header 'X-API-Key: <x-api-key>'

{
  "job_id": "<string>",
  "status": "<string>",
  "progress": {},
  "result": [
    {
      "domain": "<string>",
      "status": "<string>",
      "account_id": 123,
      "name": "<string>",
      "is_new_account": false,
      "fields_updated": [
        "<string>"
      ]
    }
  ],
  "error_message": "<string>"
}