Persondata — Search by ID and name+address

Persondata wraps SPAR (Statens personadressregister), the Swedish state population register. Two lookup modes are exposed, each in XML and JSON variants.

Search by personnummer

curl -X POST https://sandbox-api.cerrtify.com/service/persondata/search/id.json \
  -H "X-API-Key: cert_..." \
  -H "Content-Type: application/json" \
  -d '{
    "idNummer": "195704133106",
    "slutAnvandarId": "agent-42"
  }'

idNummer is a 12-digit personnummer or samordningsnummer (YYYYMMDDNNNN; a hyphen before the last four digits is accepted). The format is checked before the search is sent to SPAR: anything but 12 digits is answered with 400 and the error code invalid_idnummer. The number in the example is a test person in SPAR's test environment. slutAnvandarId is your internal end-user identifier — SPAR requires it for audit trails.

Search by name + address

When you don't have a personnummer:

curl -X POST https://sandbox-api.cerrtify.com/service/persondata/search/name-address.json \
  -H "X-API-Key: cert_..." \
  -H "Content-Type: application/json" \
  -d '{
    "fornamn": "Anna",
    "mellanEfternamn": "Andersson",
    "utdelningsadress": "Storgatan 1",
    "postort": "Stockholm",
    "postnr": "11122",
    "slutAnvandarId": "agent-42"
  }'

Choose parts of the answer

The JSON variants take the field delar: a list of numbers that says which parts of each person post you want back. Ask only for what you need.

curl -X POST https://sandbox-api.cerrtify.com/service/persondata/search/id.json \
  -H "X-API-Key: cert_..." \
  -H "Content-Type: application/json" \
  -d '{
    "idNummer": "195704133106",
    "slutAnvandarId": "agent-42",
    "delar": [1, 4]
  }'

• Without delar the answer holds parts 1–4.
• PersonId, Sekretessmarkering, SkyddadFolkbokforing and SenasteAndringSPAR are always included.
• What SPAR releases at all depends on what Skatteverket has approved for your organisation. A part you are not entitled to is missing from the answer even if you ask for it.
• An unknown number is answered with 400 and the error code invalid_delar. The XML variants always pass on SPAR's whole answer and do not take delar.

The answer to the example above:

{
  "Posts": [
    {
      "PersonId": { "IdNummer": "195704133106", "Typ": "PERSONNUMMER" },
      "Sekretessmarkering": "NEJ",
      "SkyddadFolkbokforing": "NEJ",
      "SenasteAndringSPAR": "2021-09-25",
      "Namn": [
        {
          "DatumFrom": "2021-09-25",
          "DatumTill": "9999-12-31",
          "Aviseringsnamn": "Efternamn3542, Christina Birgitta",
          "Fornamn": "Christina Birgitta Ulrika",
          "Tilltalsnamn": "20",
          "Mellannamn": "Thomeaus",
          "Efternamn": "Efternamn3542"
        }
      ],
      "Folkbokforingsadress": [
        {
          "SvenskAdress": {
            "DatumFrom": "2021-09-25",
            "DatumTill": "9999-12-31",
            "Utdelningsadress2": "Gatan142 8",
            "PostNr": "11146",
            "Postort": "STOCKHOLM"
          }
        }
      ]
    }
  ],
  "UUID": "27462246-5b1a-4379-8faf-09aba4cba964"
}

A part that SPAR repeats is a list. The entry valid now comes first and has DatumTill 9999-12-31; older entries follow. Empty fields are left out. If SPAR refuses the question, the answer holds Undantag with Kod and Beskrivning instead of posts, and if a name search has too many hits it holds OverstigerMaxAntalSvarsposter.

Test persons in sandbox

In sandbox the searches go to Skatteverket's test environment for SPAR. It holds made-up test persons, and Skatteverket publishes the list in the document Testfall för personsökning i kundtestmiljön (version 9.1, 2025-09-09) on SPAR's page about Personsök. The table shows what each test person is for and which part (delar) the data comes in. A dash means the data is always included.

• According to Skatteverket's test cases, relations are only released when the search is made with permission for relations.
• The test cases hold no person with property or income, so expect parts 9 and 10 to be empty in sandbox.
• The list also has test cases for the name search (chapter 4) and persons with unusual names and addresses (chapter 5).

This shows which parts come back for one test person. The examples use the tool jq to print the field names in the answer:

KEY="cert_..."   # your sandbox key
for d in "[0]" "[1]" "[2]" "[3]" "[4]" "[5]" "[6]" "[7]" "[8]" "[9]" "[10]" "[1,4]" "[2,8]"; do
  printf '%-8s -> ' "$d"
  curl -s -X POST https://sandbox-api.cerrtify.com/service/persondata/search/id.json \
    -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
    -d "{\"idNummer\":\"195704133106\",\"delar\":$d}" \
    | jq -r '.error // ((.Posts[0] // {}) | keys_unsorted | join(", "))'
done

And this tries several test persons with all parts:

for id in 198007199295 197901249297 195309112489 199903672385 198604069883 201607052394; do
  printf '%s -> ' "$id"
  curl -s -X POST https://sandbox-api.cerrtify.com/service/persondata/search/id.json \
    -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
    -d "{\"idNummer\":\"$id\",\"delar\":[0]}" \
    | jq -r '.error // ((.Posts[0] // {}) | keys_unsorted | join(", "))'
done

XML vs JSON

The .json variants parse the SPAR XML response into a stable JSON shape. The non-.json variants pass the raw SPAR XML through unmodified — useful if you need exact field fidelity for compliance.

When SPAR isn't configured

• Production, no certificate uploaded: 403 spar_not_configured. Upload your SPAR certificate and Skatteverket's numbers in the dashboard (see above).
• Sandbox: calls with a sandbox key go to Skatteverket's test environment with the platform's test certificate; you need none of your own. Clicking Aktivera SPAR i sandbox in the dashboard also adds the test certificate to your organisation and unlocks the test form there.
• 503 service_unavailable means the SPAR client could not be started on our side (for example an unreadable certificate). Check the uploaded certificate and passphrase, and contact support if it persists.