Pricing

One field. The rest fills itself.

HDL Search API looks up Swedish companies by registration number and individuals by personal identity number. The customer types one number — name, address and company details fill themselves in account and checkout.

Company lookup at checkout.

Registration number in, the whole customer out

Four fields become one.

B2B customers often mistype the company name, skip the VAT number or give an old address. The lookup gets the fields right on the very first order — and the customer data in the platform matches the register.

GET /v2/search/company/{orgnr} Full company details
GET /v2/search/company?q=namn Search by company name
GET /v2/search/person/{personnr} Name and address
POST /v2/search/validate Validate a number

The lookup runs when the field loses focus, with nothing extra for the customer to press.

Consumer customer

Identity number in — name and address filled.

What gets looked up.

Fields and use

Company details

Company name, registration number, legal form, status, VAT registration number and industry code.

Addresses

The registered address for billing, plus the option of a different delivery address at checkout.

Personal data

Name and registered address from the identity number entered, for account and checkout.

Validation

Check digit and format are validated before the lookup, so typos are caught in the field itself.

Autofill at checkout

Fields fill while the customer is at the checkout — fewer steps and fewer drop-offs in the B2B flow.

Cleaner customer data

The customer record matches the register from the start, which makes invoicing and ERP sync easier.

The details carry through to the customer record.

In admin

At checkout

Fewer steps to fill in

One number instead of six fields

Buying on invoice with the right details from the start

Mistyped registration numbers are caught in the field

New B2B accounts can be approved immediately

Behind the scenes

An API to build on

The same endpoints in storefront, admin and integrations

A cache per registration number for fast responses

Every lookup is logged with its source and response time

Fields can be locked so the ERP or the register owns them

Questions about the Search API.

Common questions

What can be looked up?+

Swedish company details from a registration number or company name, and name plus registered address from a personal identity number.

How is personal data handled?+

The lookup runs on the customer’s own input in the purchase flow and is stored as customer data on the account. Lookups are logged, and identity numbers are masked in the interface.

Can the customer change what was filled in?+

Yes. The fields are prefilled but editable — for a different delivery address, say. You can lock individual fields if the register should own them.

How fast does the API respond?+

A registration-number lookup typically answers within a few hundred milliseconds, and results are cached per number to keep the checkout fast.

Can it be used outside checkout?+

Yes. The same endpoints can be used in admin for manual order entry, in customer registration and in your own integrations.

Technical demo

Test the lookup on your own customers.

Bring a few registration numbers — we run them live and show what fills in, field by field.