Apideck CLI: Query 200+ SaaS APIs from your terminal. No SDK needed. Read more

Apideck Documentation Page

Exact Online UK – Configuration Guide

Service ID: exact-online-uk

Exact Cloud business software offers accounting and industry software in the cloud for SME's on desktop, laptop, tablet and mobile apps.

How to Create OAuth Credentials for Exact Online UK

This guide will help you set up your Exact Online OAuth app for the UK Exact Online instance and add its credentials to Apideck.

Before you begin, you'll need:

  • An Exact Online account on the UK instance (start.exactonline.co.uk) with access to the App Store. This connector is pinned to the United Kingdom, so the app you register must live in the UK App Store.
  • An Exact Online developer subscription for the UK region if your app will connect consumers outside your own Exact Online instance — it is what lets you register and manage your own app and link multiple customers to it. Exact charges EUR 15 per month excluding VAT per region (confirmed August 2026 — check the developer section of the Exact Online App Store UK for the current figure before you budget). An app that only ever connects your own UK instance does not need one, and a UK subscription does not cover another country's instance.
  • A user in that instance that is allowed to authorize third-party app connections.

Which connector am I configuring? exact-online-uk has a fixed UK host and no region setting, and an app registered in the UK App Store cannot connect consumers on the Dutch, Belgian, German or any other Exact Online instance. If your consumers span several countries, use the exact-online connector — it lets each consumer pick their country with the Select your API domain connection setting — or exact-online-nl for a Netherlands-pinned integration.

How to get a test environment. Your developer subscription is itself a live environment with its own divisions, and Exact offers a 30-day free trial of Exact Online for the UK (no credit card, example data preloaded) as the closest thing to a sandbox. You register your own app for this connector from the start, so your brand is on the consent screen from your very first test connection.

1. Create the OAuth application

Sign in to Exact Online App Store

  • Sign in to the Exact Online App Store UK. The developer sign-up is reachable from the "Are you an app developer?" section at the bottom of the App Store, and Exact's Register your app article walks through it.

    Sign in

Register a test app

  • Click Register a test app (you can move it to production later)

    Register app

Configure app details

  • Enter the following details:

    • App Name: Choose a descriptive name for your app
    • Redirect URI: https://unify.apideck.com/vault/callback
    • Accept the terms and conditions

    App details

The redirect URI must be exactly https://unify.apideck.com/vault/callback. Exact rejects localhost and any non-HTTPS redirect URI, and a mismatch fails authorization. Do not add a vendor or local development URL here — Apideck handles the callback for every connection.

Get your OAuth credentials

  • After creating the app, note down the Client ID and Client Secret

    Client ID & Secret

💡 TIP: Copy the Client ID and Client Secret immediately. The Client Secret may only be visible once when you first create the app.

2. Add the credentials in Apideck

  • Open the Exact Online UK connector configuration in the Apideck Dashboard

  • Select Use your Exact Online client credentials

  • Enter the following OAuth credentials:

    • Client ID → client_id: Paste the Client ID from your Exact Online app
    • Client Secret → client_secret: Paste the Client Secret from your Exact Online app

  • Click Save settings to save your credentials

    Add OAuth credentials

Exact Online uses the same app credentials for testing and production, so keep testing on the UK instance — credentials, tokens and division ids issued on the UK host are not portable to another country's host — and be careful when testing against production data.

3. Scopes

There is nothing to select. Exact Online grants access at the app-registration level rather than per consent scope, and the connector declares the Code, Description and Division scopes itself — so there is nothing to configure either in the UK App Store registration or in Apideck.

What a connection can reach is instead bounded by the authorizing user's own Exact Online rights and by the division (administration) the connection resolves. Apideck fills the division id in automatically after authorization; your consumers never type it, and multiple companies are addressed with the x-apideck-company-id header.

4. Get your app reviewed before onboarding customers outside your own instance

A freshly registered app works immediately for consumers in the same Exact Online instance that created it — which is everything you need to build and test end to end. To connect customers on other Exact Online tenants, submit the app for Exact's internal review from the App Store; once it passes, it can serve consumers across the UK instance. Ask your Exact contact for an expected timeline so you can sequence your pilot customers around it.

Publishing the app on the Exact Online App Store is a separate, optional step with its own review process. An approved app can serve external customers without being published, so App Store publication is not on the critical path for a private integration.

5. Design notes before you go live

  • Token handling is Apideck's job. Access tokens last 10 minutes and Apideck refreshes them automatically. You do not store or rotate anything.
  • Refresh tokens are single-use and go stale after 30 days of inactivity. Each refresh invalidates the previous token, and a connection that goes unused for 30 days needs the consumer to authorize again. If your product has seasonal or low-frequency users, plan a re-authorization prompt for them.
  • Bills are read-only on this connector. Your integration can read purchase invoices from Exact Online UK but not create, update or delete them, so set that expectation with customers who expect to push bills. Check the connector's Supported Resources tab for the per-resource write coverage before you scope a feature.
  • Payments need a bank journal code. Creating payments or bill payments requires a valid bank journal code (the bank_journal_code connection setting), otherwise Exact returns an "Invalid journal" error. Decide whether you set it per connection during onboarding or expose it to your consumers.
  • Financial report classifications default to Dutch RGS headings. On a UK administration, set the Balance Sheet and Profit & Loss classification-title connection settings during onboarding; left untouched, report sections fall back to coarser groupings.
  • The UK instance caps REST messages at 9.5 MB. The larger 38 MB ceiling applies only to the Netherlands and Belgium — worth knowing if you push large attachments.
  • Call budgets are per app, per company. The per-minute and per-day limits are listed on the connector's Overview and on Exact's API limits page. Build your sync to back off on errors rather than retrying tightly.

6. Test your connection

Now that your Exact Online UK connector is configured, test the connection:

  1. Open Test Vault from the connector configuration
  2. Click Authorize to authorize the connection. There is no region to pick — this connector always uses the UK instance.

Authorize connection

  1. You will be redirected to the Exact Online (United Kingdom) domain to sign in
  2. Once authorized, the connection status changes to Connected

Connection authorized

FAQ and troubleshooting

Authorization fails with an invalid redirect or a 401. The redirect URI in your Exact app registration must be character-for-character https://unify.apideck.com/vault/callback. Exact rejects localhost and non-HTTPS values outright.

A consumer outside the UK cannot authorize. App registrations are per country instance, and this connector is pinned to the UK one. Serve those consumers through the exact-online connector with a separate app registered in their country's App Store, or through exact-online-nl for the Netherlands.

A consumer on another UK Exact Online tenant cannot connect. Until the app passes Exact's internal review it is limited to the instance that created it. Submit it for review from the App Store, and onboard those customers once it passes.

A connection that used to work now asks for authorization again. The refresh token expired after 30 days without use, or the consumer revoked access in Exact Online. The consumer needs to re-authorize; nothing in your Apideck configuration changes.

Calls start returning 429. You are over Exact's call budget for that app and company. Serialize the requests and add backoff. If a consumer legitimately needs a higher ceiling, that is a conversation about their Exact Online plan.

Still stuck? Reach out to Apideck Support.