GET /api/enrichment

Data source: Orakel's domain-enrichment pipeline. Maps Norwegian companies to web domains, LinkedIn, Facebook, technologies, and ad pixels. This endpoint exposes the pipeline state — enriched fields themselves are embedded on company records.

Request

GET /api/enrichment

Response

{
  "summary": { "confirmed": 120000, "ambiguous": 8000, "rejected": 4500 },
  "total": 132500,
  "limit": 50,
  "offset": 0,
  "data": [
    {
      "orgNumber": "912345678",
      "companyName": "Example AS",
      "status": "confirmed",
      "confidence": 92,
      "primaryDomain": "example.no",
      "linkedinHandle": "example-as",
      "facebookHandle": null
    }
  ]
}

Each row also includes confirmedDomains[], candidates[] (the full scoring ledger), stage, completedAt, brregWebsite (self-reported), and basic firmographics (orgForm, city, employees). Pipeline mechanics and confidence thresholds are documented in the enrichment source page.

Examples

curl

curl -H "Authorization: Bearer $ORAKEL_KEY" \
  "https://orakel.cloud/api/enrichment?status=ambiguous&minConfidence=40&limit=100"

JavaScript

const res = await fetch(
  "https://orakel.cloud/api/enrichment?status=ambiguous&limit=100",
  { headers: { Authorization: `Bearer ${process.env.ORAKEL_KEY}` } },
);
const { summary, data } = await res.json();

Error modes

Rate limits

Per-key RPM per tier.

Typical use cases

• QA: audit ambiguous rows and their candidate lists before promoting to confirmed.
• Coverage reporting: read summary to track enrichment completion over time.
• Targeted re-runs: identify low-confidence rows for manual review.