Orbis Delegated Access

Overview

Orbis Delegated Access integrates Strise with the Orbis API from Bureau van Dijk (BvD), providing access to global company data for search and enrichment purposes. This integration enables two core capabilities:

• Search — Find companies in the Orbis database and match them with Strise entities
• Enrichment — Enrich existing entities with additional company data, UBO information, and board roles from Orbis

Getting Your API Token

To use Orbis Delegated Access, you need an API token from Bureau van Dijk. Contact your BvD account representative to obtain the ApiToken required for authentication.

Company Search

When searching for companies via the Orbis integration, results are scored by match confidence:

• Match scores of 80% or higher are considered reliable matches
• Results are categorized into confidence levels: HIGH, MEDIUM, and LOW

Search via Connect API

Use the companySearch mutation with the ORBIS source:

mutation {
  companySearch(input: { query: "Example Company AS", country: NO, source: ORBIS }) {
    results {
      name
      matchScore
      confidence
      externalId
    }
  }
}

Enrichment

The Orbis enrichment process retrieves the following data:

• Basic company data — Name, registration number, address, incorporation date, industry codes
• UBOs (Ultimate Beneficial Owners) — Individuals with 10% or more ownership, including direct and indirect ownership chains
• Roles — Board members and key personnel, mapped using the BvD BoardMnemonic classification system

Enrichment via Connect API

Use the companyEnrichGlobalEntity mutation to enrich a company with Orbis data:

mutation {
  companyEnrichGlobalEntity(input: { companyId: "company-strise-id", externalId: "orbis-bvd-id" }) {
    company {
      name
      ubos {
        name
        ownershipPercentage
      }
      roles {
        name
        roleType
      }
    }
  }
}

What Gets Stored

When entities are enriched through Orbis, Strise generates deterministic IDs based on the source data to prevent duplicate records. If an entity already exists in the Strise Knowledge Graph with matching identifiers, the existing record is updated rather than creating a new duplicate.

This ensures data consistency across multiple enrichment runs and prevents fragmentation of entity records.