Appearance
Support
Draft
The support channels on this page are being confirmed. Until then, use the contact address below for everything.
Where to ask
| You need | Where |
|---|---|
| Help with the REST API, the MCP servers, the skills or embedded white label | contact@salaxy.com — say it is a developer question |
| A commercial agreement, partnership or demo | salaxy.com |
| To check whether something is a known issue first | Availability |
What you set up yourself, and what you ask for
| Self-service | Ask Salaxy | |
|---|---|---|
| Test company account | Create an account in the test environment | — |
| Access token for development | Password flow | — |
| Signing certificate for single sign-on | In the Salaxy web application, Settings → Authorisations — see Impersonation | — |
| Password flow in production | — | Manual registration |
| Trusted partner role (account creation from your system) | Not needed in test | Required in production — Account creation |
| Federation provider role (banks, payment providers) | Any account in test, for now | Contract and role — Federation |
| A payment channel for your integration | palkkausManual for trying things out | Your production channel |
| Embedded white label design | — | Salaxy implements your design as part of the partnership — Designs |
| Access to the MCP servers | Browser sign-in: a free demo account for the demo servers, your Salaxy account for production — see MCP authentication | — |
| The sub-processor list | — | Given to commercial partners — GDPR roles |
Reporting a problem
Include what someone needs to reproduce it — and nothing that identifies a real person:
- Environment and host — test, demo or production (
test-secure.salaxy.com…), see Environments. - When — date and time, with the time zone.
- What you called — method and path, or for MCP the client and the tool name.
- What came back — the HTTP status and the full error body (
error,messageHtml,validation), see Errors. - The request — the body, with personal identity codes, names, bank accounts and salaries removed or replaced by test values.
- Your account id and, where relevant, the calculation or payroll id.
- What you expected instead.
Never send credentials
Do not put an access token, password, private key or certificate in a support message, an issue or an AI chat. If one has leaked, create a new one and tell Salaxy.
Security issues
Report a suspected vulnerability privately to contact@salaxy.com and do not publish details until Salaxy has replied. Include the same facts as for a bug — without real personal data.

