Appearance
Get a test account
Every path starts with a credential you can use without risk. Which one depends on how you build. Test and demo share the same test data, so nothing you do here touches real people or real money. Examples use the test environment; see Environments for demo and production.
| Path | Credential | How fast |
|---|---|---|
| Agentic | Free demo account | Two minutes |
| REST API | Test company account | A few minutes |
| Embedded white label | The same test company account | A few minutes |
| Partner integration | Partner account and technical account, with a certificate | Set up with Salaxy |
Agentic: MCP and skills
You need a free demo account. You sign in in the browser when you connect your client to a demo MCP server, so you never paste a password or a token into a chat. The demo uses sample data: nothing real is paid or reported.
Follow Connect a client. The tools are the same in demo and production, so what you build carries over.
REST API
You need a test company account in the test environment. It takes a few minutes and uses test data only.
- Pick a real Finnish company or association from the trade register at ytj.fi and note its business ID. It is test data, so you do not need signing rights.
- Create a company, or an accounting firm if you build for accounting firms, at test.palkkaus.fi. Sign up with email and password, not Google or Microsoft.
- Complete the onboarding wizard: enter a made-up personal identity code
ddmmyy-nnn*(a real date, any three digits and*for the checksum), then choose any authentication method except "Testing ID".
After the first verification the test environment sends no emails, and verification is not required, so a made-up address such as yourname@example.com works. Full steps: 1. Create an account.
Then get an access token with the password flow: 2. Authenticate. The token lasts 48 hours and has no refresh token; see Tokens.
Embedded white label
You need the same test company account as the REST API path, and an access token from the password flow. The embedded UI needs the token only on its first load, in the URL hash.
Follow Create an account, then Embedded white label: quick start. In production your backend gets the token through impersonation instead.
Partner integration
A partner serves many customer companies, so a single test company is not enough. You need:
- a partner account and one or more technical accounts for the test environment, set up together with Salaxy;
- a digital certificate for the technical account. You create it yourself in the Salaxy web application under Settings → Authorisations, and your server uses it to sign the JWT it exchanges for an access token.
The trusted partner role, which lets your system create customer accounts, is not needed in test. It is required in production; see Partner-initiated account creation.
Keep the private key in your backend secret store. Never ship it to a browser or commit it to git. A test certificate works only in test and demo, and a production certificate only in production, so create one per environment.
What to ask Salaxy, and when, is in Support. The setup topics are in Partner and technical accounts.
Check
- You can sign in to the test environment, or your MCP client lists the demo tools.
- You have an access token and one authenticated call succeeds.
- You know which environment each credential belongs to.

