exact-online-uk
Exact Online UK (via Apideck)
Access Exact Online UK through Apideck's Accounting unified API — one of 34 Accounting connectors that share the same method surface. Code you write here ports to Access Financials, Acumatica, banqUP and 30 other Accounting connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Exact Online UK plumbing.
Beta connector. Exact Online UK is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.
Quick facts
- Apideck serviceId:
exact-online-uk - Unified API: Accounting
- Auth type: oauth2
- Status: beta
- Gotchas: page
- Exact Online UK docs: https://support.exactonline.com
- Homepage: https://www.exact.com/uk
When to use this skill
Activate this skill when the user explicitly wants to work with Exact Online UK — for example, "create an invoice in Exact Online UK" or "reconcile payments in Exact Online UK". This skill teaches the agent:
- Which Apideck unified API covers Exact Online UK (Accounting)
- The correct
serviceIdto pass on every call (exact-online-uk) - Exact Online UK-specific auth and coverage caveats
For the full method surface (parameters, pagination, filtering), use your language SDK skill:
apideck-node,apideck-python,apideck-dotnet,apideck-java,apideck-go,apideck-php, orapideck-rest
For the raw OpenAPI spec:
- Accounting: https://specs.apideck.com/accounting.yml · API Explorer
Minimal example (TypeScript)
import { Apideck } from "@apideck/unify";
const apideck = new Apideck({
apiKey: process.env.APIDECK_API_KEY,
appId: process.env.APIDECK_APP_ID,
consumerId: "your-consumer-id",
});
// List invoices in Exact Online UK
const { data } = await apideck.accounting.invoices.list({
serviceId: "exact-online-uk",
});
Portable across 34 Accounting connectors
The Apideck Accounting unified API exposes the same methods for every connector in its catalog. Switching from Exact Online UK to another Accounting connector is a one-string change — no rewrite, no new SDK.
// Today — Exact Online UK
await apideck.accounting.invoices.list({ serviceId: "exact-online-uk" });
// Tomorrow — same code, different connector
await apideck.accounting.invoices.list({ serviceId: "access-financials" });
await apideck.accounting.invoices.list({ serviceId: "acumatica" });
This is the compounding advantage of using Apideck over integrating Exact Online UK directly: code against the unified Accounting API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
Exact Online UK via Apideck Accounting
UK-specific variant of Exact Online. Use this connector when the user's Exact instance is on the UK data center. Coverage mirrors exact-online.
When to use this vs exact-online
| User scenario | Use |
|---|---|
| User's division is in the UK | exact-online-uk |
| User's division is in the Netherlands | exact-online-nl |
| User's division is in Belgium or other EU | exact-online |
Entity mapping + coverage
Identical to exact-online. See that skill for the full mapping table and coverage highlights.
Key UK-specific behaviors:
- VAT handling: UK 20% / 5% / 0% rates; Brexit-era rules (reverse charge on EU imports) handled through
tax-rates. - Making Tax Digital (MTD) compliance: UK divisions may have MTD-specific fields on invoices (HMRC submission). Use Proxy for MTD submission endpoints not covered by the unified model.
- Currency: typically GBP-denominated; multi-currency supported for international customers.
Auth notes
- Type: OAuth 2.0, managed by Apideck Vault
- Data center:
start.exactonline.co.uk. Wrong-DC errors = wrong connector variant.
Example: list customers with invoices due in 30 days
const { data: invoices } = await apideck.accounting.invoices.list({
serviceId: "exact-online-uk",
filter: { status: "open" },
});
Verifying coverage
Not every Accounting operation is supported by every connector. Always verify before assuming a method works:
curl 'https://unify.apideck.com/connector/connectors/exact-online-uk' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}"
See apideck-connector-coverage for patterns around UnsupportedOperationError and connector-specific fallbacks.
Escape hatch: Proxy API
When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call Exact Online UK directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Exact Online UK's own API:
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: exact-online-uk" \
-H "x-apideck-downstream-url: <target endpoint on Exact Online UK>" \
-H "x-apideck-downstream-method: GET"
See Exact Online UK's API docs for available endpoints.
Sibling connectors
Other Accounting connectors that share this unified API surface (same method signatures, just change serviceId):
access-financials (beta), acumatica (beta), banqup (beta), campfire (beta), clearbooks-uk (beta), digits (beta), dualentry, exact-online, and 25 more.
See also
- Accounting OpenAPI spec · API Explorer
apideck-connector-coverage— programmatic coverage checksapideck-best-practices— architecture, Vault, pagination, error handlingapideck-node— TypeScript / Node SDK patterns- Exact Online UK official docs
More from apideck-libraries/api-skills
apideck-connector-coverage
Check Apideck connector API coverage before building integrations. Use when determining which operations a connector supports, comparing connector capabilities, or diagnosing why an API call fails with a specific connector. Teaches agents to query the Connector API for real-time coverage data.
18apideck-best-practices
Best practices for building Apideck integrations. Covers authentication patterns, pagination, error handling, connection management with Vault, webhook setup, and common pitfalls. Use when designing or reviewing any Apideck integration regardless of language.
18apideck-rest
Apideck Unified REST API reference for any language. Use when building integrations with accounting software (QuickBooks, Xero, NetSuite), CRMs (Salesforce, HubSpot, Pipedrive), HRIS platforms (Workday, BambooHR), file storage (Google Drive, Dropbox, Box), ATS systems (Greenhouse, Lever), e-commerce, or any of Apideck's 200+ connectors using direct HTTP calls. Covers authentication headers, CRUD operations, cursor-based pagination, filtering, sorting, error handling, rate limiting, pass-through parameters, and webhooks. Language-agnostic — works with curl, fetch, axios, httpx, or any HTTP client.
16apideck-portman
API contract testing with Portman by Apideck. Use when generating Postman collections from OpenAPI specs, writing contract tests, variation tests, integration tests, fuzz testing, or setting up CI/CD API test pipelines. Portman converts OpenAPI 3.x specs into Postman collections with auto-generated test suites.
14apideck-node
Apideck Unified API integration patterns for TypeScript and Node.js. Use when building integrations with accounting software (QuickBooks, Xero, NetSuite), CRMs (Salesforce, HubSpot, Pipedrive), HRIS platforms (Workday, BambooHR), file storage (Google Drive, Dropbox, Box), ATS systems (Greenhouse, Lever), e-commerce, or any of Apideck's 200+ connectors. Covers the @apideck/unify SDK, authentication, CRUD operations, pagination, filtering, webhooks, and Vault connection management.
14apideck-codegen
Generate typed API clients from Apideck OpenAPI specs using code generators. Use when the user wants to generate custom SDK clients, typed models, API stubs, or server scaffolding from Apideck's published OpenAPI specifications. Covers openapi-generator, Speakeasy, and Postman import workflows.
14