In addition to the service's error codes, there are also rejection codes that are returned if the requested consumer or company is not active. These codes apply to both consumers and companies.
Example response (200 OK):
{
"error": {
"code": "S3",
"text": "Spärrad",
"detail": "2025-03-24, Utsatt för bedrägeri"
}
}| Response Code | Code | Text | Detail |
|---|---|---|---|
| 200 OK | S2 | Skyddad | Skyddad person. |
| 200 OK | S3 | Spärrad | yyyy-mm-dd, Utsatt för bedrägeri |
| 200 OK | S4 | Avliden | yyyy-mm-dd |
| 200 OK | S5 | Tekniskt avregistrerad | - |
| 200 OK | S6 | Utvandrad | yyyy-mm-dd |
| 200 OK | S7 | Personnummerbyte | - |
It's possible to receive information on consumers and sole traders despite the rejection codes S2 and/or S6, depending on your GetData block settings:
- S2 (Protected consumers): The response will contain all available information except name and address
- S6 (Emigrated consumers): The response will contain the last known information
When your block is configured to allow these statuses, you will receive an HTTP 200 OK response with both the error object (containing the rejection code) and a report object (containing available data). If the block does not allow these statuses, the response will contain only metaData and error without a report.
| Response Code | Code | Text/Description |
|---|---|---|
| 200 OK | S200 | Inaktivt |
| 200 OK | S231 | Likvidation avslutad |
| 200 OK | S241 | Fusion avslutad |
| 200 OK | S291 | Konkurs avslutad |
| 200 OK | S292 | Konkurs avslutad med överskott |
| 200 OK | S300 | Avregistrerat |
| 200 OK | S336 | Bolaget avfört enl 13:18 aktiebolagslagen |
| 200 OK | S337 | Bolaget avfört |
| 200 OK | S350 | Avfört enligt 17 kap 2 st handelsregisterlagen |
| 200 OK | S351 | Avfört enligt 11 kap 18 § lag om ek. föreningar |
| 200 OK | S353 | Avregistrerat p.g.a. ny innehavare |
| 200 OK | S354 | Avfört p.g.a. fusion med utländskt företag |
| 200 OK | S360 | Avfört p.g.a. utländskt företags likvidation/konkurs |
| 200 OK | S361 | Avfört, verksamheten har upphört |
| 200 OK | S362 | Avfört, filialen saknar verkställande direktör |
| 200 OK | S363 | Avfört, enligt domstolsbeslut |
| 200 OK | S364 | Avfört, årsredovisning saknas |
| 200 OK | S370 | Bolaget avfört på eget begäran |
| 200 OK | S371 | Bolaget avfört av Bolagsverket |
| 200 OK | S373 | Avfört |
| 200 OK | S374 | Avfört, omregistrerat till bankaktiebolag |
| 200 OK | S377 | Avregistrat p.g.a. ombildning |
| 200 OK | S391 | Upplöst genom delning |
All company rejection codes return HTTP 200 OK responses. The rejection status is communicated through the error.code and error.text fields in the response body.
Whether you receive a report alongside the error depends on your GetData block settings:
- If the status is allowed on your block: You will receive both
error(containing the rejection code and status details) andreport(containing available company data) - If the status is not allowed on your block: You will receive only
metaDataanderrorwithout areport
Clients should check for the presence of the error object even on HTTP 200 responses, and inspect whether report is present to determine if partial data is available.
The RE99 code indicates that real estate (fastighet) data could not be retrieved from an external service. Unlike other rejection codes, RE99 can return under different HTTP status codes depending on whether other data sections were successfully retrieved.
In standard format requests (legacyformat=false or omitted), when the real estate service fails but other block sections are successfully retrieved, the API returns HTTP 200 OK with a partial success response:
- The response includes both an
errorobject (containing RE99) and areportobject - Real estate sections in the
reportwill be empty or cleared - All other requested sections remain populated with available data
Example partial success response:
{
"metaData": {
"apiLogId": 547635,
"timeStamp": "2026-07-21T09:15:00",
"resource": "GetData (1217)",
"method": "GET",
"requestUrl": "https://se-webservice.apps.creditsafe.com/getdata?blockname=COMPANY_BLOCK&searchnumber=5565144408",
"lodCreated": false
},
"error": {
"code": "RE99",
"text": "Kan inte hämta fastighetsdata"
},
"report": {
"basicInformation": {
"organizationNumber": "5565144408",
"companyName": "Example AB"
},
"financialData": {
/* populated with available data */
},
"realEstate": {
/* empty or cleared due to service failure */
}
}
}If the real estate failure prevents building any report data at all, the API returns HTTP 503 with only metaData and error (no report). See the Error Codes page for details.
When legacyformat=true, real estate failures return HTTP 500 with error code 14 (internal error) instead of RE99. This maintains backward compatibility with the old SOAP service behavior.
For standard format requests: Always check the HTTP status code first. If HTTP 200, inspect whether a report is present alongside the error. Process the available data sections and handle the real estate data gap gracefully in your application.
For legacy format requests: Real estate failures will appear as HTTP 500 with code 14, not as RE99.