Rillet

Rillet (via Apideck)

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

Beta connector. Rillet 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: rillet
• Unified API: Accounting
• Auth type: apiKey
• Status: beta
• Apideck setup guide: Connection guide
• Gotchas: page
• Rillet docs: https://rillet.com
• Homepage: https://rillet.com/

When to use this skill

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

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

Portable across 34 Accounting connectors

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

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

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

Rillet via Apideck Accounting

Rillet is a modern SaaS finance platform (general ledger + revenue recognition) targeting B2B SaaS companies. Deep coverage via Apideck.

Entity mapping

Rillet entity	Apideck Accounting resource
Invoice	invoices
Bill	bills
Bill Payment	bill-payments
Credit Note	credit-notes
Payment	payments
Journal Entry	journal-entries
Account	ledger-accounts
Customer	customers
Supplier	suppliers
Item	invoice-items
Tax Rate	tax-rates
Expense	expenses
Subsidiary	subsidiaries
Bank Account	bank-accounts
Bank Feed Statement	bank-feed-statements
Company Info	company-info
P&L, Balance Sheet	profit-and-loss, balance-sheet

Coverage highlights

• ✅ Full CRUD on invoices, bills, payments
• ✅ Credit notes
• ✅ Journal entries
• ✅ Expenses
• ✅ Multi-subsidiary
• ✅ Bank feeds for reconciliation
• ✅ Financial reports (P&L, Balance Sheet)
• ⚠️ Revenue recognition schedules (Rillet's signature feature) — not in unified; use Proxy
• ❌ SaaS metrics (ARR, MRR) — Rillet-specific; use Proxy

Auth notes

• Type: API key, managed by Apideck Vault
• Organization binding: one Rillet organization per connection.
• B2B SaaS focus: Rillet's model assumes subscription revenue. Customers without subscription semantics may not use all features.

Example: fetch P&L for YTD

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

Escape hatch: Proxy API

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

See Rillet'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 Rillet
• 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
• Rillet official docs