Yuki (via Apideck)

Access Yuki 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 Yuki plumbing.

Beta connector. Yuki 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: yuki
• Unified API: Accounting
• Auth type: apiKey
• Status: beta
• Apideck setup guide: Connection guide
• Gotchas: page
• Yuki docs: https://api.yukiworks.nl
• Homepage: https://www.yuki.nl/

When to use this skill

Activate this skill when the user explicitly wants to work with Yuki — for example, "create an invoice in Yuki" or "reconcile payments in Yuki". This skill teaches the agent:

1. Which Apideck unified API covers Yuki (Accounting)
2. The correct serviceId to pass on every call (yuki)
3. Yuki-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, or apideck-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 Yuki
const { data } = await apideck.accounting.invoices.list({
  serviceId: "yuki",
});

Portable across 34 Accounting connectors

The Apideck Accounting unified API exposes the same methods for every connector in its catalog. Switching from Yuki to another Accounting connector is a one-string change — no rewrite, no new SDK.

// Today — Yuki
await apideck.accounting.invoices.list({ serviceId: "yuki" });

// 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 Yuki 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.

Yuki via Apideck Accounting

Yuki is a Dutch cloud accounting and bookkeeping platform, strong in automated document processing and NL/BE SMB markets.

Entity mapping

Yuki entity	Apideck Accounting resource
Sales Invoice	invoices
Purchase Invoice	bills
Journal Entry (GB-mutation)	journal-entries
GL Account	ledger-accounts
Customer (Debtor)	customers
Supplier (Creditor)	suppliers
BTW code	tax-rates
Cost centre	tracking-categories
Company (Administration)	company-info
Attachments	attachments

Coverage highlights

• ✅ CRUD on invoices, bills, customers, suppliers
• ✅ Journal entries and Dutch BTW handling
• ✅ Tracking categories (cost centres)
• ✅ Document attachments (Yuki's OCR output)
• ❌ Automated document recognition workflow (Yuki's signature feature) — not exposed; use Proxy
• ❌ Bank reconciliation rules — use Proxy

Auth notes

• Type: API key, managed by Apideck Vault
• Administration-scoped: Yuki API keys are tied to a single administration (tenant). Multi-admin customers need one connection per admin.
• Permission scope: key inherits the generator's role — admin-level access recommended for full coverage.

Example: list invoices for a specific period

const { data } = await apideck.accounting.invoices.list({
  serviceId: "yuki",
  filter: { updated_since: "2026-01-01T00:00:00Z" },
});

Escape hatch: Proxy API

When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call Yuki directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Yuki'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: yuki" \
  -H "x-apideck-downstream-url: <target endpoint on Yuki>" \
  -H "x-apideck-downstream-method: GET"

See Yuki'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

• Apideck connection guide for Yuki
• Accounting OpenAPI spec · API Explorer
• apideck-connector-coverage — programmatic coverage checks
• apideck-best-practices — architecture, Vault, pagination, error handling
• apideck-node — TypeScript / Node SDK patterns
• Yuki official docs