---
title: "Create an enrichment"
method: POST
path: "/api/v2/supersearch-enrichment/"
tags: ["SuperSearchEnrichment"]
---

# Create an enrichment

`POST /api/v2/supersearch-enrichment/`

Create an enrichment for a specific resource (list or campaign). This is the main endpoint for adding enrichments to resources. The enrichments are automatically run after creation.

## Request body

- object
  - `resource_id` string, uuid, required — Unique identifier for the resource (list or campaign)
  - `type` 'work_email_enrichment' | 'fully_enriched_profile' | 'email_verification' | 'joblisting' | 'technologies' | 'news' | 'funding' | 'engagement_score' | 'ai_enrichment' | 'custom_flow' — Enrichment type to add to the resource
  - `limit` number — Maximum number of leads to enrich.
  - `filters` object[] — Filters to apply to the enrichment
  - `custom_flow` string[] — Custom flow to apply to the enrichment
  - `integration_actions` object — Provider-keyed integration actions to run against the resource. Mutually exclusive with `type` — either run a built-in enrichment via `type` or supply `integration_actions` to run one or more provider actions. Outer keys are provider IDs (e.g. `findymail`, `apify`); inner keys are action IDs offered by that provider (e.g. `findymail_find_email`). Each action requires a `mapping` object whose keys are the action's declared input fields and whose values are the lead column names to read from.

## Response `200`

Default Response

- object
  - `id` string, required — Unique identifier for the enrichment
  - `limit` number — The maximum number of leads to enrich
  - `organization_id` string, uuid, required — Organization ID that created this enrichment
  - `resource_id` string, uuid, required — Unique identifier for the entity to enrich leads into
  - `enrichment_payload` object — The enrichment configuration payload
    - `joblisting` boolean — Whether job listing enrichment is enabled
    - `email_verification` boolean — Whether email verification is enabled
    - `work_email_enrichment` boolean — Whether work email enrichment is enabled
    - `fully_enriched_profile` boolean — Whether fully enriched profile is enabled
    - `custom_flow` string[]

## Other responses

- `401` — This request is unauthorized (either the Authorization header is missing or invalid, or the API key has been revoked)
- `402` — This request cannot be fulfilled because the workspace does not have an active paid plan
- `404` — The requested resource was not found
- `429` — You have exceeded the rate limit. Please check the rate limit docs for more information.

---

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