Language and localization

Language and localization

The Partner API v2 responds in English by default. This is the headline difference in tone from v1 (which is Swedish-only).

Default: English

With no language hint, localized text fields (parameter name, groupName, description, period, and similar) come back in English:

curl -H "X-Api-Key: $SEDIS_API_KEY" \
  "https://api.sedis.se/v2/bolagsanalys/parameters?code=NX71"

{ "data": [ { "code": "NX71", "name": "Total return", "groupName": "Key figures", "description": "..." } ], "page": 1, "pageSize": 50, "totalCount": 1, "totalPages": 1 }

Requesting Swedish

Two equivalent ways to ask for Swedish — pick whichever suits your client:

Query parameter:

curl -H "X-Api-Key: $SEDIS_API_KEY" \
  "https://api.sedis.se/v2/bolagsanalys/parameters?code=NX71&lang=sv"

Accept-Language header:

curl -H "X-Api-Key: $SEDIS_API_KEY" -H "Accept-Language: sv" \
  "https://api.sedis.se/v2/bolagsanalys/parameters?code=NX71"

{ "data": [ { "code": "NX71", "name": "Totalavkastning", "groupName": "Nyckeltal", "description": "..." } ], "page": 1, "pageSize": 50, "totalCount": 1, "totalPages": 1 }

The ?lang= query parameter takes precedence if both are present.

Fallback rule

Localized text resolves as English if present, otherwise Swedish (*En ?? *Sv). So:

• In English mode (default), a field that has not yet been translated falls back to its Swedish source value. You may therefore occasionally see a Swedish string even with no ?lang=sv — that means the English translation is not yet populated for that specific row, not that the API ignored your request.
• In Swedish mode (?lang=sv), you always get the Swedish value.

Sedis continually fills in English translations, so English coverage improves over time. No code change is needed on your side as coverage grows.

What is not localized

• Field names are always English camelCase regardless of ?lang= (groupName stays groupName).
• Identifiers and codes (companyId, parameterCode, sedisId, quarterId) are language-neutral.
• A few proper nouns stay Swedish because they have no clean English equivalent — most notably Jämförelseobjekt (a cloned benchmark zone), documented in The Comp Composite & clone lineage. Resource paths like /samlingar and /jamforelseobjekt are domain proper nouns, not translatable strings.
• Source names (sourceName) are surfaced verbatim as stored (e.g. "Nils Holgersson") — never translated.

propertyTypeName matches the Swedish name

The ?propertyTypeName= filter on /fastighetsbenchmark/property-units is a case-insensitive substring match against the stored Swedish property-type name (e.g. Kontor, Bostad) — not the English label. Use the numeric ?propertyType= id filter (or the enum domain from GET /parameters/{code}) when you need a language-neutral match. See The Comp Composite & clone lineage.