The GetSignatory REST API provides information about authorized company signatories and the combinations in which they can legally sign on behalf of a company.
Use this API to validate signing authority before agreements are accepted, helping ensure legal validity in digital and manual workflows.
GetSignatory helps you:
- Validate authorized signers before contracts are approved
- Understand signing combinations required for legally valid signatures
- Support compliance processes with structured signatory data
Typical use cases include:
- Verifying who can sign for a company in legal or financial processes
- Enforcing signing rules in contract workflows
- Supporting internal controls for onboarding and credit processes
The Integration team is available to assist with technical questions during development and post-launch. You can reach them at integration@creditsafe.se
JSON Communication:
- GetSignatory is a REST API that communicates using JSON
- The responsibility to map the response and apply signing logic lies with the customer
Coverage and Completeness:
- Signing combinations are extracted from text registered with Bolagsverket
- It is not always possible to retrieve all signing combinations
- The API response indicates coverage as
complete,partial, ornone - Integrations should handle all coverage levels safely
Coverage by company type:
| Company Type | Complete | Partial or None |
|---|---|---|
| Limited companies ("Aktiebolag") | 99.0% | 1.0% |
| Sole traders ("Enskilda firmor") | 100% | 0% |
| Trading companies ("Handelsbolag") and partnerships ("Kommanditbolag") | 95.5% | 4.5% |
| Other company types ("Ovriga bolagsformer") | 95.6% | 4.4% |
The coverage in the table above reflects the proportion of companies where signatory information is available.
Handling Missing Data:
- Returned parameters, lists, or objects may be empty
- Returned parameters, lists, or objects may be omitted from the response
- Ensure your integration handles both empty values and missing fields safely
API Evolution:
- Creditsafe may add new information, tags, or attributes to the service at any time without prior notice
- Existing elements will not be removed without notification in advance
- The order of elements in the JSON response is not guaranteed to be consistent across requests
Implementations using this service should primarily process requests sequentially, particularly when handling batch operations with large request volumes. Sequential processing helps ensure predictable behaviour and optimal use of the service.
A limited degree of parallelism is supported; however, client implementations must be designed to tolerate temporary request throttling if traffic exceeds allowed thresholds. Clients are expected to pause request execution and resume once additional requests can be accepted.
Creditsafe reserves the right to restrict access for implementations that generate excessive load or do not properly handle enforced request limitations. Please read more about rate limiting in the section about error codes.
Before using GetSignatory, you must authenticate using the CONNECT Authenticate API. The generated JWT token is valid for 1 hour and can be used across Creditsafe Sweden REST APIs.
Authentication endpoint:
POST https://connect.creditsafe.com/v1/authenticateSee the Authenticate API documentation for details.
- Review Sandbox for test environment setup
- Review Request and Response for request format and response structure
- Review MetaData for tracing and support fields
- Review Health Check for service monitoring
- Review Error Codes for troubleshooting
For technical questions during development or post-launch:
- Email: integration@creditsafe.se