How to find a Norwegian company's org number from its name or LEI

Every company endpoint in Apier is keyed on a 9-digit organisation number. When you hold a name, an address from an invoice, or an LEI instead, GET /api/v1/company/resolve turns it into org-number candidates you can choose from.

The endpoint never picks a company for you. It returns a ranked list, each candidate with the evidence for the match, and you decide which one is right.

Step 1 — Resolve a nameCopy Anchor Link

curl -H "Authorization: Bearer $APIER_API_KEY" \
  "https://www.apier.no/api/v1/company/resolve?name=Nordic%20Widgets"

The answer lists up to ten candidates from Brønnøysund's name search. Each one carries:

• org_number, name, org_form, municipality and status from the register;
• evidence.name_similarity, a score from 0 to 1 for how close the registered name is to yours once case, punctuation and legal-form words (AS, ASA, ENK, NUF and similar) are removed;
• evidence.name_match: exact, normalised_exact or partial.

Candidates are sorted by rank: name similarity first, then the address evidence, then org number, so the same query always gives the same order.

Step 2 — Add an address to separate similar namesCopy Anchor Link

curl -H "Authorization: Bearer $APIER_API_KEY" \
  "https://www.apier.no/api/v1/company/resolve?name=Nordic%20Widgets&address=0155%20Oslo"

With address, each candidate's evidence.address_match says how your address compares with the registered business address, word by word: matches (every word found), partial, differs, not_registered when the register holds no business address, or not_given when you sent no address. The evidence shows the registered postal code and place only, never the street lines, and your address is used for the comparison only: it is never echoed in the answer or stored.

Step 3 — Resolve an LEICopy Anchor Link

curl -H "Authorization: Bearer $APIER_API_KEY" \
  "https://www.apier.no/api/v1/company/resolve?lei=APIER0EXAMPLE0000042"

The answer gives the org number GLEIF records for the LEI, from Apier's daily archive of GLEIF's Level 1 records for Norwegian entities, with GLEIF's registration_status and entity_status. check_status is verified when GLEIF's registration status is ISSUED and stale otherwise. GLEIF is named as the source; its data is CC0 1.0 and nothing here implies GLEIF's endorsement.

Rules and billingCopy Anchor Link

• Give exactly one of name and lei. address is only read together with name. Any other parameter is refused with 400 VALIDATION_FAILED.
• No match, or an LEI with no current Norwegian mapping, is 404 NOT_FOUND.
• A 200 is billed as one company read. A 404 or any error is never billed. See pricing.
• The endpoint needs an API key with the read:brreg scope.