dualentry
Dualentry integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcil
SKILL.mdskills/dualentry/SKILL.md
GitHubDualentry (via Apideck)
Access Dualentry 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 Dualentry plumbing.
Quick facts
- Apideck serviceId:
dualentry - Unified API: Accounting
- Auth type: apiKey
- Apideck setup guide: Connection guide
- Gotchas: page
- Dualentry docs: https://dualentry.com
- Homepage: https://www.dualentry.com/
At a glance
- Implementation difficulty: moderate — API Key Authentication — Credential Generated by the Consumer's DualEntry Administrator
- Vendor partnership required: no — Apideck holds an approved partnership with DualEntry, so no application or certification is required from you.
- Apideck-managed credentials: not available — Each consumer supplies their own API key; there is no shared Apideck credential.
- Account type required: Any DualEntry plan. Multi-company tenants supported; scope to a Default Company or the whole tenant.
- Consumer access level: Organisation administrator — only an admin can generate the API key, via Settings > Organization > Developer access.
- Sandbox: available (signup) — A separate Development environment at api-dev.dualentry.com with its own organisations and API keys; a production key will not authenticate there.
- Costs: No separate API fee — bundled into the DualEntry subscription, which lists Open API as a plan feature.
- Rate limits: 300 requests/min per API key across all endpoints; 60 requests/min per endpoint; invoice create/update capped at 2/min.
- Authentication: Sent in the X-API-KEY header, not OAuth. The key is a long-lived organisation credential with no expiry.
- Webhooks: No webhooks — not supported by DualEntry's API.
Important to know:
- The API key is not self-service for you: the consumer's own DualEntry administrator must generate it, and DualEntry shows it only once at creation — if it is lost, a new key must be issued and the old one revoked.
- On a multi-company tenant, a read that does not name a company returns records from every company in the tenant. Set a Default Company on the connection, or send an x-apideck-company-id header per request.
- DualEntry offers no free trial. Every plan includes accountant-led implementation instead, so evaluating the platform means going through their onboarding rather than self-serving.
Facts synced from Apideck's connector metadata API —
GET /connector/connectors/dualentry(overviewfield) is the live, authoritative version.
When to use this skill
Activate this skill when the user explicitly wants to work with Dualentry — for example, "create an invoice in Dualentry" or "reconcile payments in Dualentry". This skill teaches the agent:
- Which Apideck unified API covers Dualentry (Accounting)
- The correct
serviceIdto pass on every call (dualentry) - Dualentry-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 Dualentry
const { data } = await apideck.accounting.invoices.list({
serviceId: "dualentry",
});
Portable across 34 Accounting connectors
The Apideck Accounting unified API exposes the same methods for every connector in its catalog. Switching from Dualentry to another Accounting connector is a one-string change — no rewrite, no new SDK.
// Today — Dualentry
await apideck.accounting.invoices.list({ serviceId: "dualentry" });
// 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 Dualentry 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.
Dualentry via Apideck Accounting
Dualentry is a cloud accounting platform offering modern, double-entry bookkeeping with comprehensive multi-entity support. Broad Apideck coverage.
Entity mapping
| Dualentry entity | Apideck Accounting resource |
|---|---|
| Invoice | invoices |
| Bill | bills |
| Bill Payment | bill-payments |
| Credit Note | credit-notes |
| Payment | payments |
| Journal Entry | journal-entries |
| Ledger Account | ledger-accounts |
| Customer | customers |
| Supplier | suppliers |
| Item | invoice-items |
| Purchase Order | purchase-orders |
| Expense | expenses |
| Subsidiary | subsidiaries |
| Attachments | attachments |
Coverage highlights
- ✅ Full CRUD on invoices, bills, payments (incl. bill payments)
- ✅ Credit notes
- ✅ Journal entries
- ✅ Purchase orders
- ✅ Expenses
- ✅ Multi-subsidiary support
- ✅ Attachments on transactions
- ⚠️ Financial reports (P&L, Balance Sheet) — not in current mapping; use Proxy
- ❌ Payroll — separate surface
Auth notes
- Type: API key, managed by Apideck Vault
- Organization binding: one Dualentry organization per connection.
- Multi-subsidiary: subsidiaries are exposed as a first-class resource; use
subsidiariesto fetch and filter.
Example: create a multi-line bill
const { data } = await apideck.accounting.bills.create({
serviceId: "dualentry",
bill: {
supplier_id: "sup_abc",
bill_date: "2026-04-18",
due_date: "2026-05-18",
line_items: [
{ description: "Service A", quantity: 1, unit_price: 500 },
{ description: "Service B", quantity: 2, unit_price: 250 },
],
currency: "USD",
},
});
Escape hatch: Proxy API
When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call Dualentry directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Dualentry'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: dualentry" \
-H "x-apideck-downstream-url: <target endpoint on Dualentry>" \
-H "x-apideck-downstream-method: GET"
See Dualentry'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), exact-online, exact-online-nl (beta), and 25 more.
See also
- Apideck connection guide for Dualentry
- Accounting OpenAPI spec · API Explorer
apideck-connector-coverage— programmatic coverage checksapideck-best-practices— architecture, Vault, pagination, error handlingapideck-node— TypeScript / Node SDK patterns- Dualentry official docs