Skip to content

Integration overview ​

An integration has two parts: a build path, which decides who builds the user interface, and the integration topics, which you work through in order. Each topic page starts with an overview, then shows the options under "Which fits you?". Skip the options that do not apply to you.

Choose your build path ​

The two build pathsTwo build paths side by side. Embedded Salaxy UI: Salaxy Business for companies and Salaxy Pro for accounting firms run inside your product, in an iframe or opened from it with single sign-on; less work. Your own UI: you build the screens on the REST API; more work. In both paths the Salaxy payroll engine does the calculation, the payments and the Incomes Register filing. Under it, your payment channel can fetch the invoices, pay them and report back.1Embedded Salaxy UILess work2Your own UIMore workYOUR PRODUCT — IFRAME OR SINGLE SIGN-ONSalaxy Businessfor companiesSalaxy Profor accounting firmsYOUR PRODUCTYour own screenson the REST APIREST APISalaxy payroll enginecalculation, payments and Incomes Register filingYour payment channeloptional: fetch invoices, pay, report back
Purple: Salaxy builds it. Grey: you build it. The payroll engine is the same in both paths; the payment channel is optional in each.
1. Embedded Salaxy UI2. Your own UI
Who builds the UISalaxy: Salaxy Business for companies and Salaxy Pro for accounting firms, in an iframe in your product under your own design, or at least opened from your product with single sign-onYou, on the REST API
What you buildSingle sign-on for your users, customer account creation (and accounting firm accounts for Salaxy Pro), and usually a payment channel and the monthly accounting data pull. Employees and payrolls are done in the Salaxy UIEvery payroll screen: customer onboarding, employments, payrolls and calculations, and the payment status. Salaxy's onboarding screens can handle the company's sign-up
EffortLessMore
ExampleA property management, accounting or financial management system that adds payroll for its customers and their accounting firmsA financial or HR app with its own payroll screens
Start withEmbedded white labelREST API — getting started

Both paths are Finland only. For other countries, and for anything conversational, use the agentic path: see MCP or REST?. An agent can also do a single job inside either path — for example, a payroll assistant inside your product.

Paths can be combined. For example, an embedded integration also imports workers or worktime through the API (Worktime import), or your own UI covers some tasks and the embedded Salaxy UI the rest.

Salaxy Pro also works standalone: accounting firms sign in to it directly. That is not an integration, so it is not a build path here.

What every integration needs ​

Salaxy sets these up with you once, before you build. Each has its own topic page.

ItemWho does whatTopic
Partner account and technical accountsSalaxy creates them; you create the certificate your backend signs withPartner and technical accounts
Service modelSalaxy sets it up: what the customer companies you bring get, and what is lockedService models
Payment channelSalaxy pays from a customer funds account, or your channel pays; you build your channelPayment channels and SEPA payment files
Accounting modelSalaxy sets it up: where the accounting entries goAccounting models

Partner or company? ​

  • Partner: you serve many customer companies, often through their accounting firms. You need the one-time setup topics below. If accounting firms sit between you and the companies (three-tier), you also need the Pro API for the accounting firm view.
  • Company: you connect your own systems to your own Salaxy account. You can skip most of the one-time setup.

Integration topics ​

The topics are in the order an integration usually goes. Some topics say which build paths need them; the others apply to every path. Building with a coding agent? Start with Integration in a day with a coding agent.

1. Setup and onboarding (one-time)

2. People — for your own UI; in the Salaxy UIs, employees are kept on screen, unless you import them

3. Payroll

4. Payments

5. Reporting and filings

6. Optional features

7. Go live

The API rules ​

Every REST integration follows the same rules for errors, queries and paging, retries and idempotency, and events and polling. They are in the Reference, next to the REST API reference.

Every page is also available as Markdown: add .md to its URL — a folder page such as white-label/ is white-label/index.md. Index for LLMs: llms.txt. Questions: Support.