Proff shareholder API

Use the Proff shareholder API to retrieve published shareholder or ownership records for the selected entity. Choose the documented selection using company registration number (org_number), shareholder person ID (person_id); refine the result with country code (country). Ownership records keep the named holder and reported stake associated with the applicable entity and reporting period, helping distinguish the source's disclosed position from an assumption about real-time beneficial ownership. Compare published ownership positions, identify major holders and retain the reporting period attached to each stake. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.

Selected price
$0.002 / billing creditPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Optional parameters (8)
The shareholder company's organisation number (9 digits). Give `org_number` or `person_id`.
A person shareholder's id (digits) from /proff/v1/search `shareholder_matches` (type Person).
no (Norway; the only country with shareholder data).
0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
1 skips the 24-hour cache and fetches live.
JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON exports are not exposed.
Native CSV/NDJSON record selector; it has no effect on this JSON-only product.

Sample response

{
  "cached": false,
  "city": "OSLO",
  "country": "NO",
  "credits_used": 1,
  "id": "912660680",
  "indirect_owners": {
    "items": [],
    "total": 0
  },
  "indirect_owners_count": 0,
  "indirect_ownerships": {
    "items": [
      {
        "country": "NO",
        "direct": false,
        "id": "830845712",
        "multiple_owners": false,
        "name": "Fabrikkveien 100 Tomt 3 AS",
        "org_number": "830845712",
        "share_pct": 100,
        "share_type": null,
        "shares": 100,
        "source": null,
        "source_date": null,
        "total_shares": 100,
        "type": "Company"
      },
      {
        "country": "NO",
        "direct": false,
        "id": "912998851",
        "multiple_owners": false,
        "name": "Posten Eiendom Trondheim AS",
        "org_number": "912998851",
        "share_pct": 100,
        "share_type": null,
        "shares": 543133,
        "source": null,
        "source_date": null,
        "total_shares": 543133,
        "type": "Company"
      },
      "… 248 more"
    ],
    "total": 3725
  },
  "indirect_ownerships_count": 3725,
  "name": "Nærings- og Fiskeridepartementet",
  "note": "Each list holds up to 250 entries, as the source shows them.",
  "org_number": "912660680",
  "owners": {
    "items": [],
    "total": 0
  },
  "owners_count": 0,
  "ownerships": {
    "items": [
      {
        "country": "NO",
        "direct": true,
        "id": "984661185",
        "multiple_owners": false,
        "name": "Posten Bring AS",
        "org_number": "984661185",
        "share_pct": 100,
        "share_type": "Ordinære aksjer",
        "shares": 3120000,
        "source": "Skatteetaten",
        "source_date": "2025-12-31",
        "total_shares": 3120000,
        "type": "Company"
      },
      {
        "country": "NO",
        "direct": true,
        "id": "986392912",
        "multiple_owners": false,
        "name": "Baneservice AS",
        "org_number": "986392912",
        "share_pct": 100,
        "share_type": "Ordinære aksjer",
        "shares": 80000,
        "source": "Skatteetaten",
        "source_date": "2025-12-31",
        "total_shares": 80000,
        "type": "Company"
      },
      "… 16 more"
    ],
    "total": 18
  },
  "ownerships_count": 18,
  "status": "ACTIVE",
  "type": "Company",
  "url": "https://www.proff.no/shareholder/912660680?type=Company"
}

Response result

Response structure

Inferred from examples
  • cachedboolean
  • citystring
  • countrystring
  • credits_usedinteger
  • idstring
  • indirect_ownersobject
    • itemsunknown[]
    • totalinteger
  • indirect_owners_countinteger
  • indirect_ownershipsobject
    • items(object | string)[]
      • countrystring
      • directboolean
      • idstring
      • multiple_ownersboolean
      • namestring
      • org_numberstring
      • share_pctinteger
      • share_typenull
      • sharesinteger
      • sourcenull
      • source_datenull
      • total_sharesinteger
      • typestring
    • totalinteger
  • indirect_ownerships_countinteger
  • namestring
  • notestring
  • org_numberstring
  • ownersobject
    • itemsunknown[]
    • totalinteger
  • owners_countinteger
  • ownershipsobject
    • items(object | string)[]
      • countrystring
      • directboolean
      • idstring
      • multiple_ownersboolean
      • namestring
      • org_numberstring
      • share_pctinteger
      • share_typestring
      • sharesinteger
      • sourcestring
      • source_datestring
      • total_sharesinteger
      • typestring
    • totalinteger
  • ownerships_countinteger
  • statusstring
  • typestring
  • urlstring

Loading related APIs…

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Proff shareholder API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.