Skip to main content
POST
Execute Enrichment

Overview

Execute one or more marketplace enrichment integrations to enhance entity data with information from external providers. Enrichments add additional fields to the entity without performing risk assessment. This endpoint supports batch execution of multiple enrichments in a single request, optimizing cost and performance.

Endpoint

Authentication

Requires a valid API key in the Authorization header:

Request Body

string
required
UUID of the entity (company or person) to enrich
array<string>
required
Array of enrichment integration codes to execute. See Provider Codes Reference for available codes.At least one integration code is required.
object
Optional additional parameters for the integrations (default: {})

Response

boolean
Whether all enrichments succeeded
array<object>
Array of individual enrichment results. Each result contains:
  • success (boolean) - Whether this enrichment succeeded
  • enrichmentId (string) - ID for viewing enrichment details
  • integrationCode (string) - The integration code that was executed
  • result (object) - Enrichment result data:
    • fieldsEnriched (array<string>) - List of fields that were enriched
    • dataQuality (object) - Data quality metrics
    • summary (string) - Human-readable summary
    • enrichmentData (object) - The enriched data
  • executionTime (number) - Execution time in milliseconds
  • costCents (number) - Cost in cents
  • error (object, optional) - Error details if failed
number
Total cost for all enrichments in cents
number
Total execution time for all enrichments in milliseconds
object
Result of rules execution when the rules engine runs after enrichment (if configured). When present, includes:
  • success (boolean) - Whether rules executed successfully
  • rulesTriggered (number) - Number of rules that were triggered
  • alerts (array) - Alerts generated by rules
  • riskScore (number) - Final calculated risk score
  • decision (string) - Final decision (APPROVE, REJECT, HOLD, REVIEW_REQUIRED)
  • rulesExecutionSummary (object) - When rules ran, detailed summary; see below.
object
At the root of the response (same as transactions API). Same value as rulesResult.rulesExecutionSummary. Only present when rules ran after enrichment. Summary of which rules matched (hit) vs did not match (no hit), executed actions, and total score.
  • rulesHit (array) - Rules whose conditions were met. Each item: name, description, score, priority, category, status, conditions, actions.
  • rulesNoHit (array) - Rules evaluated but conditions not met. Same structure as rulesHit.
  • actionsExecuted (object) - Aggregated executed actions: alerts, suggestion, status, assignedUser, customKeys (array of strings, optional) — custom action keys from rules that matched; for integrations/workflows.
  • totalScore (number) - Sum of score of all rules that hit (excluding shadow).

Examples

Execute Single Enrichment

Execute Multiple Enrichments (Batch)

Response Example

Successful Enrichment

Partial Failure (Some Enrichments Failed)

Error Responses

404 Not Found - Entity Not Found

400 Bad Request - Invalid Integration Code

401 Unauthorized

Pricing

  • Each enrichment has its own cost (see integration catalog)
  • Failed enrichments are NOT charged
  • Costs are deducted from your organization’s token balance
  • 1 token = 100 cents = $1.00 USD

Best Practices

  1. Batch Enrichments: Execute multiple enrichments in one request to optimize performance
  2. Error Handling: Check individual success fields in results array
  3. Cost Management: Monitor totalCostCents to track usage
  4. Provider Selection: Choose enrichments based on your entity’s country and required fields
  5. View Details: Use the enrichmentId to view complete enrichment details later

Automatic Rules Execution

When enrichments succeed, the rules engine may automatically execute based on your risk matrix configuration. The rulesResult field contains the rules execution outcome.

Use Cases

Progressive Data Enrichment

Multi-Provider Strategy

Next Steps