To retrieve the authorized signatory for a specific company, you must first authenticate your user account.
Please refer to the Authenticate API documentation for details on how to authenticate and obtain a token.
Note that this step differs from earlier versions of the GetSignatory REST API. The generated token can be used across all Creditsafe Sweden REST APIs including DateCheck, GetData, SearchEngine, GetSignatory, GetUnitData, and SPAR.
GetSignatory Endpoint:
https://se-webservice.apps.creditsafe.com/getsignatoryHealth Check:
https://se-webservice.apps.creditsafe.com/getsignatory/healthThe GetSignatory REST API uses a single GET method to retrieve the company's authorized signatories.
Endpoint:
GET /getsignatoryExample Request:
HEADER: Authorization: Bearer <token>
URL: https://se-webservice.apps.creditsafe.com/getsignatory?searchnumber=5565144408&transactionid=X123
Method: GETThe table below describes each parameter included in the requests.
| Parameter | Data type | Max length | Required | Description |
|---|---|---|---|---|
| searchnumber (query) | String | 10 | Yes | Organization number (10 digits) |
| 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. For this service it is only affecting error responses. Available languages: sv or en |
In the sandbox version of this API, only the parameters searchnumber and transactionid are actively supported. All other parameters included in the request will be ignored without error or warning.
Developers are encouraged to structure their requests as they would in a production environment, including all expected parameters. This ensures consistency and simplifies the transition to production usage. However, it is important to understand that in sandbox mode, unsupported parameters will not influence the response and should not be relied upon for testing behavior or data validation.
The response contains a metaData object with request information and a report object with the company's signatory information.
{
"metaData": {
"apiLogId": 542900,
"timeStamp": "2026-07-15T14:26:33",
"resource": "GetSignatory (1227)",
"method": "GET",
"requestUrl": "https://se-webservice.apps.creditsafe.com/getsignatory?searchnumber=5565144408"
},
"report": {
"companyId": "5566443388",
"coverage": "complete",
"adminSign": [
[
{
"name": "Testersson, Karl",
"positions": [
{
"roleCode": 5,
"roleName": "Ledamot"
},
{
"roleCode": 12,
"roleName": "Verkställande direktör"
}
],
"personalNumber": "198208161212"
}
]
],
"combinations": [
[
{
"name": "Testersson, Karl",
"positions": [
{
"roleCode": 5,
"roleName": "Ledamot"
},
{
"roleCode": 12,
"roleName": "Verkställande direktör"
}
],
"personalNumber": "198208161212"
}
]
]
}
}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 |
| method | String | Specifies the HTTP method used for the request |
| requestUrl | String | The complete URL of the request sent to Creditsafe |
The report object contains the company's signatory information:
| Parameter | Data type | Description |
|---|---|---|
| companyId | String | The company's organization number as sent in the request (digits only) |
| coverage | String | Specifies if all combinations could be identified. Available values: complete, partial, none |
| adminSign | Array | Persons allowed to sign for the company only in administrative matters. Contains arrays of signing combinations |
| combinations | Array | Possible signing combinations (max 5,000). Contains arrays of signing combinations |
For each person in the adminSign or combinations arrays:
| Parameter | Data type | Description |
|---|---|---|
| name | String | Name of the signatory |
| positions | Array | Function(s) of the signatory. Contains objects with roleCode and roleName |
| personalNumber | String | Person number of signatory |
Parameters with a null value are hidden in the responses of Creditsafe's REST APIs.
The GetSignatory API provides detailed information about who is authorized to sign for a company:
- Coverage indicator - Shows whether all signing combinations were successfully identified
- Administrative signatories - The
adminSignarray lists persons who can sign only for administrative matters - Signing combinations - The
combinationsarray shows all possible ways the company can be legally bound (max 5,000 combinations) - Multiple roles - A single person can have multiple positions/roles, shown in the
positionsarray - Role codes - Each position includes both a numeric
roleCodeand descriptiveroleNamein Swedish
Use this information to understand signing authority and validate who can legally commit the company to agreements.