Store credentials
Store username and password credentials for accessing the Transparenzregister API.
These credentials will be used for subsequent requests to retrieve company documents.
Credential names are user-scoped; the reserved name sandbox cannot be used.
Credentials are validated against Transparenzregister before they are persisted.
Store Transparenzregister credentials
Stores Transparenzregister login credentials so that subsequent extract requests can authenticate on your behalf. Use the body fieldname to identify this credential set. If omitted, name defaults to default. You can store multiple named credential sets (e.g. per client). Submitting the same name again overwrites the stored credentials for that name without affecting extracts already in flight.
The reserved name sandbox cannot be used — it is reserved for test-mode extracts via X-Credential-Name: sandbox on the order extract endpoint. Using sandbox as a credential name returns 400.
Your credentials are encrypted at rest. The plaintext values never touch our database — only encrypted ciphertext is persisted, and every decryption is logged and auditable.
Responses
Authorizations
API Key Authentication Provide your API key as a Bearer token in the Authorization header.
Body
Credentials for accessing the Transparenzregister API.
Username for Transparenzregister API access. Example: "compliance@example.com"
Password for Transparenzregister API access.
Name to identify this set of credentials. Allows storing multiple
Transparenzregister credentials per user (e.g., for different accounts
or clients). Defaults to 'default' if not provided.
Cannot be sandbox because that name is reserved for test-mode extracts.
Example: "client_a"
Response
Credentials stored successfully

