Skip to content
Last updated

Requests and Responses

Authentication

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.


Production URLs

GetSignatory Endpoint:

https://se-webservice.apps.creditsafe.com/getsignatory

Health Check:

https://se-webservice.apps.creditsafe.com/getsignatory/health

Request Methods

The GetSignatory REST API uses a single GET method to retrieve the company's authorized signatories.

GetSignatory Request

Endpoint:

GET /getsignatory

Example Request:

HEADER: Authorization: Bearer <token>
URL: https://se-webservice.apps.creditsafe.com/getsignatory?searchnumber=5565144408&transactionid=X123
Method: GET

Request Parameters

The table below describes each parameter included in the requests.

ParameterData typeMax lengthRequiredDescription
searchnumber (query)String10YesOrganization number (10 digits)
transactionid (query)String14NoCustomer'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)String3NoSets the language of the response. For this service it is only affecting error responses. Available languages: sv or en
Sandbox Parameter Behavior

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.


Response (Successful)

The response contains a metaData object with request information and a report object with the company's signatory information.

HTTP Response code: 200 OK

{
  "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"
        }
      ]
    ]
  }
}

Response Parameters

The response contains two main sections:

metaData

The metaData object contains request information for tracing and troubleshooting:

ParameterData typeDescription
apiLogIdIntegerUnique identifier for the Creditsafe API log. Refer to this ID when contacting support
timeStampDateTimeThe exact time when the request was processed by Creditsafe. Format: YYYY-MM-DDTHH:MM:SS
resourceStringIndicates which service delivered the report
methodStringSpecifies the HTTP method used for the request
requestUrlStringThe complete URL of the request sent to Creditsafe

report

The report object contains the company's signatory information:

ParameterData typeDescription
companyIdStringThe company's organization number as sent in the request (digits only)
coverageStringSpecifies if all combinations could be identified. Available values: complete, partial, none
adminSignArrayPersons allowed to sign for the company only in administrative matters. Contains arrays of signing combinations
combinationsArrayPossible signing combinations (max 5,000). Contains arrays of signing combinations

Signatory Person Parameters

For each person in the adminSign or combinations arrays:

ParameterData typeDescription
nameStringName of the signatory
positionsArrayFunction(s) of the signatory. Contains objects with roleCode and roleName
personalNumberStringPerson number of signatory
Null Values

Parameters with a null value are hidden in the responses of Creditsafe's REST APIs.


Understanding the Response

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 adminSign array lists persons who can sign only for administrative matters
  • Signing combinations - The combinations array 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 positions array
  • Role codes - Each position includes both a numeric roleCode and descriptive roleName in Swedish

Use this information to understand signing authority and validate who can legally commit the company to agreements.