CtrlK
BlogDocsLog inGet started
Tessl Logo

digits

Digits 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 reconcile invoices, bills, payments, ledger accounts, and journal entries in Digits. Routes through Apideck with serviceId "digits".

87

Quality

86%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Digits (via Apideck)

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

Beta connector. Digits 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: digits
  • Unified API: Accounting
  • Auth type: oauth2
  • Status: beta
  • Digits docs: https://digits.com
  • Homepage: https://www.digits.com/

When to use this skill

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

  1. Which Apideck unified API covers Digits (Accounting)
  2. The correct serviceId to pass on every call (digits)
  3. Digits-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:

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 Digits
const { data } = await apideck.accounting.invoices.list({
  serviceId: "digits",
});

Portable across 34 Accounting connectors

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

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

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

Digits via Apideck Accounting

Digits is a modern US-focused accounting platform built for real-time financial visibility, popular with startups and venture-backed companies. Apideck coverage focuses on reporting and ledger views.

Entity mapping

Digits entityApideck Accounting resource
Accountledger-accounts
Journal Entryjournal-entries
Customercustomers
Vendorsuppliers
Dimensiontracking-categories
P&L, Balance Sheetprofit-and-loss, balance-sheet

Coverage highlights

  • ✅ Ledger accounts (chart of accounts)
  • ✅ Journal entries
  • ✅ Customers, suppliers
  • ✅ Financial reports (P&L, Balance Sheet)
  • ✅ Dimensions (tracking categories)
  • ❌ Invoices, bills, payments — Digits is primarily a reporting/analytics layer on top of QuickBooks/Xero; transactional writes go through those source systems
  • ❌ AI-driven insights — Digits' signature feature; proprietary, not exposed

Auth notes

  • Type: OAuth 2.0, managed by Apideck Vault
  • Workspace binding: one Digits workspace per connection.
  • Upstream source: Digits typically syncs from QuickBooks or Xero. For transactional writes, use those connectors directly; use Digits for unified reporting views.

Example: fetch P&L for the quarter

const { data } = await apideck.accounting.profitAndLoss.get({
  serviceId: "digits",
  filter: { start_date: "2026-01-01", end_date: "2026-03-31" },
});

Escape hatch: Proxy API

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

See Digits'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), dualentry, exact-online, exact-online-nl (beta), and 25 more.

See also

Repository
apideck-libraries/api-skills
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.