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/

At a glance

Implementation difficulty: moderate — API Key Authentication + API Access Enabled per Organisation by Rillet
Vendor partnership required: no
Apideck-managed credentials: not available — Each consumer connects with their own Rillet organisation API key; there is no app to register.
Account type required: A Rillet account. Any plan works; there is no edition gate on API access.
Consumer access level: Admin access to Organization Settings, which is where API keys are created.
Sandbox: available — A separate sandbox environment at sandbox.api.rillet.com with its own API keys, arranged through your Rillet team.
Costs: No API-specific fee. Rillet itself is a paid platform and does not publish pricing.
Rate limits: 60 requests per rolling one-minute window; requests above it return HTTP 429.
Authentication: Presented as a Bearer token in the Authorization header; not OAuth. Keys are scoped to a single Rillet organisation.
Webhooks: No webhooks

Important to know:

API access is not self-service. Rillet has to enable it for each organisation before any API key can be created, so your consumer starts by contacting their Rillet team rather than by opening a settings page.

Facts synced from Apideck's connector metadata API — GET /connector/connectors/rillet (overview field) is the live, authoritative version.

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:

Which Apideck unified API covers Rillet (Accounting)
The correct serviceId to pass on every call (rillet)
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.