Before you start
Choose a small set of incomplete records that represents real ambiguity in your data. Decide which fields are required and which confidence level is safe for automatic acceptance.
1. Create a Sandbox key
Create a key with enrich:write, jobs:read, and evidence:read scopes. Store the full value immediately; the workspace shows it only once.
2. Submit representative records
Send stable client record IDs and the identity fields you already know. Requested facts belong in the profile, not in provider-specific request options.
curl -X POST https://sandbox.enrich.nordicdevhouse.com/v1/enrichment-jobs \
-H "Authorization: Bearer enrich_test_••••••••" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: crm-pilot-001" \
-d '{
"profile": "verified-company@1",
"output_format": "jsonl",
"records": [{"id": "crm_1842", "fields": {"company_name": "Northstar Logistics Oy", "country": "FI"}}]
}'3. Inspect facts and evidence
Treat accepted facts, unresolved candidates, and review cases as separate states. Persist the job and entity IDs so retries, webhook events, and audit records can be correlated.
{
"job_id": "enr_01J7A4M2",
"records": [{
"id": "crm_1842",
"entity_id": "org_fi_2841842_1",
"facts": {"primary_domain": {"value": "northstar.example", "confidence": 0.99}},
"review_required": ["employee_range"]
}]
}4. Promote the profile
Review low-confidence and conflicting examples, tune the acceptance policy, and then promote the same versioned profile to Production.