Appearance
Partner and technical accounts
Every partner integration starts from two kinds of Salaxy account and one certificate. Salaxy creates the accounts. You create the certificate, and your server uses it to get access tokens. Do this once per environment, before any other integration work. Examples use the test environment; see Environments for demo and production.
The accounts
| Account | What it is | Who uses it |
|---|---|---|
| Partner account | Your top-level admin account. It is created against your company's business ID, with a power of attorney. | It owns the technical accounts and is not used in the daily API flow. |
| Technical account | The API-facing account under the partner account, with the same business ID. | Your server signs in as it. It owns the payment channel that serves every customer company below it. |
- A partner account can have several technical accounts.
- A technical account has no access back up to the partner account.
- Technical accounts are created by Salaxy. There is no API for creating one.
How customer companies and accounting firms sit below the technical account: Account structure.
Who does what
| Step | Done by |
|---|---|
| Create the partner account | Salaxy |
| Create the technical account or accounts | Salaxy, with you |
| Create the digital certificate for the technical account | You, in the Salaxy web application or through the API |
| Check the set-up with a first token | You |
The payment channel, service models and accounting models are also provisioned by Salaxy. See the next topics in this section.
Test and production
Each environment has its own accounts. The test accounts should exist when the project starts, so verify that before you start coding. Production accounts are separate; you switch to them when you go live (Go-live checklist).
- A certificate works in one environment family only. A test certificate fails in production, and a production certificate fails in test. Create one for each.
- Test and demo accept the same kind of certificate. Only production has its own.
The digital certificate
The certificate proves that a request comes from your technical account. Your server signs a JWT with its private key and exchanges the JWT for an access token. The full flow, with claims and a code sample, is in Impersonation flow for SSO. This page covers only what to create.
What you create
- Sign in to the Salaxy web application with a user linked to the technical account. In test: test.palkkaus.fi.
- Go to Settings → Authorisations and create a new digital certificate.
- Pick the format:
.pfx(for .NET and Java; you set a password in the dialog) or.pem(for Node.js and Python; a zip with<thumbprint>.crt,<thumbprint>.keyand<thumbprint>.pem). - Store the private key in your backend's secret store.
Never share the private key
Do not send it to anyone, put it in the browser or commit it to git. Anyone who has it can act for your customers.
What you send to Salaxy: nothing. The certificate is registered on the technical account when you create it.
What the certificate looks like
| Property | Value |
|---|---|
| Subject | CN=<technical account id>. The certificate identity is the account. |
| Key | RSA 2048, SHA-256 signature |
| Issuer | A Salaxy root CA: a development root in test and demo; the production root in production |
Rotation and revocation
- An account can hold several certificates at once, each revoked on its own. To rotate without downtime, add the new certificate, switch your server to it and then delete the old one.
- Deleting a certificate removes it immediately. There is no revocation list: if a key leaks, delete that certificate and issue a new one.
- Salaxy sets no expiry per certificate, so the rotation schedule is yours to agree in the project.
Production: let Salaxy sign your own key
The PEM endpoint also accepts a certificate signing request (CSR) in the password field of the request body. Salaxy signs it and returns no private key, so the production key is generated in your own infrastructure and never travels over the network. This path is API-only; the web application always generates the key pair itself.
| Method | Path | Purpose |
|---|---|---|
POST | /v03/api/accounts/certificate | Issue a certificate as a .pfx file. The password is required |
POST | /v03/api/accounts/certificate/pem | Issue a certificate as a .pem zip, or sign your CSR |
GET | /v03/api/accounts/certificate | List the account's certificates |
DELETE | /v03/api/accounts/certificate/{id} | Delete a certificate |
Test it
- Create a test certificate for your technical account, as above.
- Build and sign a JWT with
issandsubset to the technical account id, and exchange it athttps://test-secure.salaxy.com/oauth2/token(Impersonation flow for SSO). - Call
GET https://test-secure.salaxy.com/v03/api/session/currentwith the token as a Bearer token. A200response with the technical account incurrentAccountshows that the set-up works.
For a customer company, you sign in with sub set to the customer's account id; see Customer account creation.
Checklist
- The test partner account and technical account exist, and you know the technical account id.
- You created a certificate for each environment, and each private key is only in your backend's secret store.
- Your server exchanges a signed JWT for an access token and gets a
200from/v03/api/session/current. - You have a plan for rotating certificates: add the new one, switch, delete the old one.
- Test and production use separate certificates and separate account ids in your configuration.
Next: Account structure

