Integrations · Accounting & ERP
Yuki API: connect Yuki to your webshop, CRM and documents
I connect Yuki through Yuki's web services, with an API key and an administration ID you create in Yuki yourself. n8n has no built-in Yuki node, so the integration is custom work in n8n. Yuki counts calls per day; the integration uses that budget sparingly.
CustomVia the API, custom-built
What you can do with the Yuki API
- Deliver sales invoices from your webshop or CRM into Yuki
- Upload purchase invoices and receipts from your email automatically
- Keep contacts in sync with your CRM
- Fetch outstanding debtors for reminders or a dashboard
- Fetch balances and revenue for reporting
How the integration works
In Yuki, under Settings, Web services, you create a key with permissions at portal, domain or administration level. The integration signs in, gets a session and then uses the web service that fits the task: Sales for sales invoices, Upload for documents, Contact for relations. Because Yuki counts calls per day, the integration bundles work and only checks what is necessary.
Facts about the Yuki API
Checked on 2 November 2026 against the official documentation. Limits, prices and versions change; the source is listed per row.
| Fact | What the documentation says | Source |
|---|---|---|
| Authentication | SOAP web services with an API key and administration ID, created in Yuki under Settings, Web services; permissions at portal, domain or administration level. TLS 1.2 or higher. | Yuki: API link |
| Session | Signing in returns a session ID; the lifetime is not in the documentation. | Yuki: API link |
| Rate limits | 1,000 calls per day per domain by default, free. Web service add-on: 1,000 to 5,000 per day; Web service Extended: 5,000 to 10,000 per day. | Yuki: API link |
| Webhooks | Not in the official documentation. | Yuki: API link |
| Test environment | Not in the official documentation. | Yuki: API link |
| Web services | Twelve web services, including Accounting, Sales (sales invoices as UBL), Upload, Contact, Projects, VAT and Purchase. Purchase needs a separate client ID and secret through support. | Yuki: API link |
| API cost | 1,000 calls per day free; the add-ons have no price in the documentation. The Sales web service is included free in most bundles. | Yuki: API link |
| n8n | No built-in node and no community node found; the integration runs through an HTTP step in n8n. | n8n documentation |
What you need on your side
- A portal administrator or manager in Yuki who can create a web service key at the right level
- The administration ID of the administration the integration works in
- An estimate of the number of calls per day, so we know whether the free budget is enough
- The VAT rates and ledger accounts, aligned with your accountant
Where it often goes wrong, and how I prevent it
- Daily limit: every domain has 1,000 calls per day by default. An integration that checks everything every minute burns its budget in a few hours. The integration bundles and schedules.
- Permissions at the wrong level: domain or administration permissions override portal permissions. I record up front at which level the key sits.
- Purchase separately: the Purchase web service requires separate access through Yuki support. I request that in time.
- VAT and ledger: I agree the VAT and ledger mapping with you or your accountant before anything is delivered.
In practice
A Yuki integration is not yet listed as In production with me. The approach is the same as for Moneybird: deliver documents and invoices with a fixed reference, use the daily budget sparingly, and send a plain-language notification when something does not arrive.
What it costs
I build a Yuki integration as one scoped process for a fixed price, from €750. Maintenance and monitoring are a monthly fee: n8n management from €250 per month, server management €145 per server. A Yuki add-on for more calls per day comes on top. All prices and what is included →
What I do not do
- I do not do your bookkeeping; the VAT and ledger mapping comes from you or your accountant.
- I do not build an integration that burns Yuki's daily budget on checks.
- I do not use operations Yuki marks as obsolete.
Frequently asked questions about the Yuki API
Does n8n have a Yuki node?
No, and no community node was found either. I connect Yuki through the web services with an HTTP step in n8n.
How many calls per day may I make in Yuki?
1,000 per domain per day by default, free of charge. With the Web service add-on up to 5,000 and with Web service Extended up to 10,000 per day. The integration bundles work, so the budget is not spent on checks.
Where do I find the API key in Yuki?
Under Settings, Web services in Yuki, together with the administration ID. Only a portal administrator or a user with management rights can create that key.
Does Yuki have webhooks?
Not according to the official documentation. The integration therefore checks at fixed intervals, within the daily budget, and keeps track of what has already been processed.
Can I send purchase invoices to Yuki automatically?
Yes, through the Upload web service. The Purchase web service, with more options, needs separate access that you request from Yuki support.
Related integrations
Often connected together
Twinfield
CustomDeliver entries and relations through the API.
More about the Twinfield integration →Exact Online
In productionSync orders, items and prices with your webshop, including customer group prices.
More about the Exact Online integration →Moneybird
CustomUpdate invoices, contacts and payments through the API.
More about the Moneybird integration →Mollie
CustomMatch payments and refunds to your invoices.
More about the Mollie integration →