To be able to do a DateCheck for a specific company or consumer, you must first authenticate your user account.
Please refer to the Authenticate API documentation for details on how to authenticate and obtain a token.
The generated token can be used across all Creditsafe Sweden REST APIs including DateCheck, GetData, SearchEngine, GetSignatory, GetUnitData, and SPAR.
Company DateCheck:
https://se-webservice.apps.creditsafe.com/datecheck/companyConsumer DateCheck:
https://se-webservice.apps.creditsafe.com/datecheck/consumerThe DateCheck REST API includes two distinct GET methods: one for consumers and one for companies.
Endpoint:
GET /datecheck/companyExample Request:
HEADER: Authorization: Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6Im…hPeGE7Ak8YtKFbA
URL: https://se-webservice.apps.creditsafe.com/datecheck/company?searchnumber=5565144408&referencedate=2020-08-29&transactionid=X123&language=sv
Method: GETEndpoint:
GET /datecheck/consumerExample Request:
HEADER: Authorization: Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6Im…hPeGE7Ak8YtKFbA
URL: https://se-webservice.apps.creditsafe.com/datecheck/consumer?searchnumber=198001010001&referencedate=2024-01-01&transactionid=X123&language=sv
Method: GETThe table below describes each parameter included in the requests for both types.
| Parameter | Data type | Max length | Required | Description |
|---|---|---|---|---|
| searchnumber (query) | String | 12 | Yes | Person number (12 digits) or organization number (10-12 digits). Only digits are allowed |
| referencedate (query) | String | 10 | Yes | The date from which the changes will be calculated. See "Important Information" regarding reference date limitations. Accepted formats: YYYY-MM-DD, YYYYMMDD, YYMMDD |
| transactionid (query) | String | 14 | No | Customer's internal information (customer/invoice number). Recommended to use this field as it can be helpful in tracking your call in Creditsafe logs |
| language (query) | String | 3 | No | Sets the language of the response. Available languages: sv (Swedish) or en (English) |
| legacyformat (query) | Boolean | - | No | If you leave this parameter out or send a false value you will get the new format used in Creditsafe REST APIs. Pass true into this parameter if you want the API to respond with the old SOAP parameter format from previous versions |
The change date in the response cannot be older than:
- 36 months for consumers or sole traders (enskilda firmor)
- 60 months for limited companies (aktiebolag), trading companies (handelsbolag), or partnerships (kommanditbolag)
The responsibility for tracking the date of the last credit decision and its outcome lies with the customer; the DateCheck REST API does not maintain this information.
It is mandatory to include a reference date in the request, which should correspond to the date of the last credit decision. The response will contain any changes that have occurred since this date.
The response format from the DateCheck REST API is the same for both consumers and companies. However, the change codes that may appear differ between the two. Please refer to the Change Categories section for the available change codes.
All successful responses include a metaData object containing request information for tracing and troubleshooting, and a report array containing the list of changes.
{
"metaData": {
"apiLogId": 542900,
"timeStamp": "2026-07-15T14:26:33",
"resource": "DateCheck Company (1219)",
"method": "GET",
"requestUrl": "https://se-webservice.apps-dev.creditsafe.com/datecheck/company?language=en&referencedate=2024-01-01&searchnumber=5565144408"
},
"report": [
{
"code": "RAT",
"description": "Rating",
"changeDate": "2022-12-02T00:00:00"
},
{
"code": "POD",
"description": "Riskprognos",
"changeDate": "2022-12-02T00:00:00"
},
{
"code": "LIM",
"description": "Limit",
"changeDate": "2022-08-22T00:00:00"
},
{
"code": "DEP",
"description": "Betalningsanmärkning E-Mål/Tredskodom",
"changeDate": "2024-06-13T00:00:00"
},
{
"code": "DEM",
"description": "Skuldsaldo E-Mål",
"changeDate": "2022-09-11T00:00:00"
},
{
"code": "DAP",
"description": "Betalningsanmärkning A-Mål",
"changeDate": "2022-10-22T00:00:00"
},
{
"code": "DAM",
"description": "Skuldsaldo A-Mål",
"changeDate": "2021-01-10T00:00:00"
},
{
"code": "CON",
"description": "Kontakt information",
"changeDate": "2022-09-09T00:00:00"
},
{
"code": "BOA",
"description": "Styrelse",
"changeDate": "2022-09-09T00:00:00"
},
{
"code": "ASI",
"description": "Firmatecknare",
"changeDate": "2022-09-09T00:00:00"
},
{
"code": "ANA",
"description": "Bokslut/Hel och delårs redovisningar",
"changeDate": "2022-08-22T00:00:00"
}
]
}The response contains two main sections:
The metaData object contains request information for tracing and troubleshooting:
| Parameter | Data type | Description |
|---|---|---|
| apiLogId | Integer | Unique identifier for the Creditsafe API log. Refer to this ID when contacting support |
| timeStamp | DateTime | The exact time when the request was processed by Creditsafe. Format: YYYY-MM-DDTHH:MM:SS |
| resource | String | Indicates which service delivered the report (e.g., "DateCheck Company (1219)" or "DateCheck Consumer (1220)") |
| method | String | Specifies the HTTP method used for the request |
| requestUrl | String | The complete URL of the request sent to Creditsafe |
The report array contains the list of changes. For each change code where a change has occurred since the reference date, the following parameters will be returned:
| Parameter | Data type | Description |
|---|---|---|
| code | String | Change code as described in the change categories |
| description | String | Description of the change code, available in English or Swedish |
| changeDate | DateTime | Date when the change occurred. Format: YYYY-MM-DDTHH:MM:SS |
Please note that parameters with a null value are hidden in the responses of Creditsafe's REST APIs.
The response from the service includes change categories along with the dates of their most recent updates. For example, if a consumer's score has changed three times since the reference date, only the most recent date will be returned.
While this information allows you to determine when a specific change occurred, it does not indicate whether the change was positive or negative.
Use the date of your last credit decision report as the referencedate in your request. If the response contains any change codes, you know changes have occurred since that report — no date comparison is needed. Both the reference date and the outcome of the last credit decision must be stored on the customer's side, as the API does not manage this logic.
If your logic manages data updates correctly, you can avoid recurring change codes by setting the reference date to the previous DateCheck request instead of the latest credit decision.