Twinfield
Service ID: twinfield
Twinfield (Sage) cloud accounting platform.
Beta — this connector is in beta. Functionality and resource coverage may change.
At a Glance
- Difficulty
- ⚠️INVOLVEDPaid Certified Partner certification with a consultant-reviewed technical audit
- Authentication
- OAuth 2.0OAuth 2.0 (OpenID Connect) authorization code flow. Each organisation has its own API host, which is resolved before any call can be made.
- Webhooks
- Virtual webhooks — created and updated events for customers and suppliers.
- Partnership Required
- Yes(Paid Certified Partner certification gates production; until it is granted, a client ID runs at 5% of the normal rate limits.)
- Partnership Application
- Wolters Kluwer Twinfield Certified Partner programme↗
- Apideck Credentials
- AvailableAvailable for development and testing — production connections run on your own certified Twinfield client ID.
- Costs
- The API certification carries a monthly subscription fee; Wolters Kluwer publishes no figure, so confirm it with their partner team when you apply.
- Sandbox Availability
- Not available(Not available self-serve — a test administration is provisioned with the certification subscription.)
- Account Type Required
- A Twinfield administration (office); registering the OAuth client ID needs a free Wolters Kluwer Account.
- Consumer Access Level
- Consumer authorizes through OAuth and supplies their Twinfield office code, since Twinfield identifies administrations by code rather than by id.
- Rate Limits
- Credit-based — 1,000 credits/minute per client ID, IP and organisation (500 per pair); reads cost 1 credit, writes 3; 20 concurrent requests.
What are Apideck credentials?
For select connectors, Apideck has established partnerships allowing you to integrate immediately without your own partnership. When using Apideck credentials, “Apideck” appears as the requesting application during OAuth. Learn more about partnership categories →
Responsibility matrix
| Task | You (Customer) | Your Consumer | Apideck |
|---|---|---|---|
| Create Wolters Kluwer Account | ✓ | — | — |
| Complete Twinfield API Certification | ✓ | — | Docs provided |
| Register & Configure OAuth Client | ✓ | — | Docs provided |
| Add Credentials to Apideck | ✓ | — | — |
| Authorize Connection (OAuth) | — | ✓ | Handles OAuth flow |
| Supply Office Code & Control Accounts | ✓ (if known upfront) | ✓ | — |
| Build via Unified API | ✓ | — | Maintains connector |
| Token Refresh | — | — | ✓ Automatic |
| Monitor Connections | ✓ Via dashboard | ✓ Can revoke anytime | Logs & alerts |
Environments
- Single environment
- Twinfield itself has no sandbox/production selector — one OAuth client ID and one set of credentials serve both testing and live use. The only change at go-live is on the Apideck side: swap Apideck's own credentials (uncertified, development and testing only) for your certified client ID. Testing always targets a real Twinfield administration rather than an isolated mock, so writes post real transactions.
🚨Important to Know About Twinfield
- Invoices, bills, journal entries, payments and bill payments can all be listed and read by id — the invoices list only returns unpaid sales invoices. Bills and journal entries can also be created; invoices, payments and bill payments are currently read-only for creation.
- A refresh token is invalidated the moment the connecting Twinfield user is deleted, disabled, locked or lets their password expire — or the organisation is deactivated. There is no warning: the first sign is an invalid_grant error, so plan a reconnect path.
- Certification is an ongoing commitment rather than a launch milestone: Wolters Kluwer deactivates an uncertified integration two weeks after notice, and re-audits certified ones every two years.
⚠️
28 gotchas across 16 resources
Connector-specific behaviors and limitations to be aware of
📦
18 supported resources
View field mappings, supported operations, and schema details