API key accounting integrations

Company Admin or Company Owner role. Available on the Team plan and above. You also need permission inside the accounting software to generate or view API credentials — typically an admin role there too.

The flow is the same for every API key integration:

1. Sign in to the accounting software and locate its API credentials section.
2. Generate or copy the credentials (key, secret, token, company ID — varies by vendor).
3. In Uku, go to Settings & Apps, find the integration card, and click Enable if it is not already on.
4. Open the integration dialog and go to the Connect or Settings tab.
5. Paste each credential into its labelled field.
6. Click Test connection to verify before saving.
7. Click Save.

If the test fails, see Troubleshooting below. After a successful save, the integration appears in the Integration column of your client list and can be enabled per client.

For details on summary task configuration and data field mapping (the same for all integrations), see Setting up accounting integrations.

Region: Norway. Tripletex uses two tokens rather than a single API key.

1. Sign in to Tripletex and go to Selskap → API-tilgang (Company → API access).
2. Generate an employee token linked to the user account that should sync data.
3. Uku already holds the consumer token as the integrating partner — you do not need to provide it.
4. In Uku, paste the employee token and choose production (or test if you are connecting a sandbox).
5. Click Test connection then Save.

What syncs: clients, products, VAT types, invoices outbound. One-way for read; invoice export sends invoices to Tripletex.

Gotcha: employee tokens have an expiration date. If sync stops, regenerate the token in Tripletex and paste the new value.

Region: Estonia, UK, global.

1. Sign in to Scoro and go to Settings → API.
2. Copy your company account ID, API key, and subdomain (the part of your Scoro URL before .scoro.com).
3. In Uku, paste all three values into the integration dialog.
4. Choose the language (Estonian, English) used for invoice exports.
5. Click Test connection then Save.

What syncs: tax rates, invoice export to Scoro. Outbound — Uku pushes invoices into Scoro; clients are not imported.

Gotcha: the subdomain is just the prefix (e.g. acme), not the full URL. Pasting the full URL will fail the connection test.

Region: Estonia, Finland, Poland (in Poland it is sold as 360 Księgowość). The Uku integration uses Merit Aktiva v1 — the v2 API is not yet wired up.

1. Sign in to Merit Aktiva and go to Company settings → Integrations.
2. Generate an API ID and an API key.
3. In Uku, paste the API ID, API key, and select the correct country (Estonia, Finland, or Poland — they are separate Merit instances and credentials do not cross over).
4. Click Test connection then Save.

What syncs: tax rates, products, summary statistics (entries, VAT entries, documents) for monthly summary tasks, invoice export, paid-invoice status updates back to Uku.

Gotcha: if the country is wrong, the test will fail with an authentication error even if the credentials themselves are correct. Each Merit country runs as a separate service.

Region: Estonia.

1. Sign in to Smart Accounts and go to the Settings area for API access.
2. Generate an API key and API secret.
3. In Uku, paste both values into the integration dialog.
4. Click Test connection then Save.

What syncs: VAT types, summary statistics (sale entries, purchase entries, bank entries, documents) for monthly summary tasks, invoice export.

Gotcha: the secret is shown only once when generated. If you lose it, you must regenerate the pair in Smart Accounts and re-paste both into Uku.

Region: Estonia, Latvia.

1. Sign in to Directo and ask your administrator to generate a personal access token scoped to the integration user.
2. In Uku, paste the access token into the integration dialog.
3. Click Test connection then Save.

What syncs: articles (products), client read, summary statistics, invoice export to Directo.

Gotcha: Directo tokens are tied to a specific company database. If your firm has multiple Directo databases, generate a separate token for each and connect them at the client level rather than at the company level.

Region: Estonia (Trigon Bank — used by accounting firms managing payment files for Estonian clients).

1. Sign in to Trigon and go to the API access section.
2. Generate or retrieve the ID token (sometimes called identity token) and the API key.
3. In Uku, paste both values and select the correct environment (production unless you are testing).
4. Click Test connection then Save.

What syncs: clients, contacts, addresses, transaction volumes (used to drive monthly summary task statistics).

Gotcha: Trigon caches transaction volumes per period. If a client looks like it is missing entries, run Reload data from the integration Settings tab to refresh the cache.

The most common causes:

• A credential was copied with leading or trailing whitespace. Re-copy directly from the source field.
• The wrong region or country is selected (Merit Aktiva especially).
• The token has been revoked or expired in the accounting software. Regenerate and paste again.
• For Scoro: the subdomain field has the full URL pasted instead of just the prefix.

Enabling the integration only allows it to be used. Data flows once you also:

• Enable the integration on a specific client (in the client view, set the Integration column to this vendor).
• Configure summary task settings on the integration Settings tab — see Setting up accounting integrations.
• Wait for the next scheduled import day, or trigger Reload data to back-fill the last 12 months.

Most token-based vendors (Tripletex, Trigon) issue tokens with an expiration date. Regenerate the token inside the accounting software, paste the new value into Uku, and re-test the connection. Smart Accounts and Merit Aktiva keys do not expire automatically, but they can be revoked if an admin rotates credentials.

Uku will start failing the next sync attempt and show an error indicator on the integration. No client data is lost; once you paste a fresh credential and the test succeeds, scheduled syncs resume.