Skip to main content
ConfigView reads your Rillet (AI-native ERP and general ledger) organization through the Rillet Accounting API (https://api.rillet.com), using an API key that a Rillet admin creates. ConfigView sends only GET requests. It never creates, changes or deletes anything in Rillet. You will end up with 1 required secret (RILLET_API_KEY) in ConfigView when setup is complete.
Scope of this integration today. ConfigView reads who has access to Rillet (members with work email, name and status), the roles and the permission list each one grants, which member holds which role for the whole organization or for a single subsidiary, the organization profile (trade name, currency, time zone), the subsidiaries, and the webhook endpoints. It does not read journal entries, invoices, bills, credit memos, customers, vendors, contracts, accounts, payments or any amount.

What you need

  • A Rillet admin who can open Organization Settings > API Access
  • Rillet API access enabled for your organization. If the page is missing, ask your Rillet team to enable it.
  • Whether you are connecting production or the sandbox. A key works for one organization and one environment; ConfigView uses the production address https://api.rillet.com.

Step 1: Open the Rillet page in ConfigView

Open ConfigView in a second browser tab and leave it open: https://{companyname}.configview.com/admin/integrations/rillet

Step 2: Create the API key

  1. In Rillet open Organization Settings > API Access and choose Create API key
  2. Name it (for example ConfigView) and switch on Read-only. ConfigView never writes.
  3. Copy the key now. Rillet shows it once.
  4. In the ConfigView tab paste it into RILLET_API_KEY under Credentials and save
The key does not expire and Rillet does not rotate it. Revoke it in the same page to cut ConfigView off.

Step 3: Connect and verify

  1. Click Connect. ConfigView creates its tables and schedules every collector at your default run time:
  1. Click Verify now. The health check reads the secret, then reads the organization and one page of members.
If a check fails:
  • 401. The key is wrong, revoked, from the other environment (sandbox vs production), or API access is not enabled for your organization.
  • 403 or 404. The key cannot read that area. Create a new key without restricting it beyond read-only.

Data Tables

Each table has a run_at column and keeps only the newest run.

Things worth knowing

Permissions are opaque. Rillet returns each permission as a colon-delimited key (for example ap:vendors:view). ConfigView stores the list and counts it; it does not interpret what a key allows. No sign-in dates. Rillet’s member list has no last sign-in or created date, so ConfigView cannot flag stale accounts. Status (active, archived, pending) is the lifecycle signal. API key and audit log. Rillet has no audit-log endpoint. Its “Get API key information” endpoint is documented without any response fields, so ConfigView does not collect it yet. Webhooks. The destination is reduced to its host. The signing token is never returned by the list call and is never stored. Rate limit. Rillet allows 600 requests a minute per API key in production (100 in the sandbox) and answers HTTP 429 beyond that. ConfigView paces itself at 120 requests a minute, waits as long as Rillet asks, and reads 100 rows per page. Pagination. Lists use cursors that expire after two hours; ConfigView reads each list in one run.

What isn’t collected

  • Journal entries, ledger accounts, invoices, bills, credit memos, payments and every amount
  • Customers, vendors, contracts and their contact details
  • Subsidiary legal names, addresses and tax ids
  • Webhook signing tokens and full webhook URLs
  • API key values