Rillet

Rillet is an AI-native ERP and accounting platform. Its REST API lets you sync core accounting records — chart of accounts, customers, vendors, invoices, bills, journal entries, contracts, bank data, and financial reports — and create new accounting records such as customers, vendors, invoices, bills, and journal entries. Nexla connects to the Rillet API to ingest these objects as data sources and to write records back as a destination.

Power end-to-end data operations for your Rillet API with Nexla. Our bi-directional Rillet connector is purpose-built for Rillet, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Rillet or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Rillet workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Rillet authenticates API requests with an API key sent as a Bearer token in the Authorization header. Requests also include an X-Rillet-API-Version header to pin the API version.

To obtain an API key:

1. Contact your Rillet team to enable API access for your organization.

2. Sign in to Rillet and open the Organization Settings page.

3. Navigate to the API Access section and create a new API key.

4. Copy the key and store it securely — you will provide it when creating your Nexla credential.

For more details, see the Rillet API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	Rillet API key, sent as a Bearer token. Contact your Rillet team to enable API access, then create a key in Organization Settings.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Rillet API key in the API Key field. This key is sent as a Bearer token in the Authorization header on every request and must be kept confidential.

   If your API key is compromised, revoke it in the Rillet Organization Settings page and generate a new one. For details on authentication and available endpoints, see the Rillet API documentation.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Rillet connector tile, then select the credential that will be used to connect to Rillet, and click Next; or, create a new Rillet credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Rillet endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Accounts

List all chart-of-accounts entries. Supports incremental sync via updated.gt.

[Rest API] List Customers

List all customers (AR). Supports updated.gt and search filters. Results are paginated via a next-cursor token.

[Rest API] List Vendors

List all vendors (AP). Supports updated.gt. Results are paginated via a next-cursor token.

[Rest API] List Invoices

List all invoices (AR). Supports updated.gt and status filters. Results are paginated via a next-cursor token.

[Rest API] List Bills

List all vendor bills (AP). Results are paginated via a next-cursor token.

[Rest API] List Journal Entries

List all general-ledger journal entries. Results are paginated via a next-cursor token.

[Rest API] List Contracts

List all revenue contracts. Results are paginated via a next-cursor token.

[Rest API] List Credit Memos

List all AR credit memos. Supports updated.gt. Results are paginated via a next-cursor token.

[Rest API] List Vendor Credits

List all AP vendor credits. Supports updated.gt. Results are paginated via a next-cursor token.

[Rest API] List Charges

List all charges. Results are paginated via a next-cursor token.

[Rest API] List Products

List all products. Results are paginated via a next-cursor token.

[Rest API] List Bank Accounts

List all bank accounts.

[Rest API] List Bank Transactions

List all bank transactions. Results are paginated via a next-cursor token.

[Rest API] List Invoice Payments

List all invoice payments across the org. Results are paginated via a next-cursor token.

[Rest API] List Reimbursements

List all reimbursements. Results are paginated via a next-cursor token.

[Rest API] List Subsidiaries

List all subsidiaries (legal entities).

[Rest API] List Tax Rates

List all configured tax rates.

[Rest API] Income Statement Report

Retrieve the income-statement (P&L) report.

[Rest API] Balance Sheet Report

Retrieve the balance-sheet report.

[Rest API] Trial Balance Report

Retrieve the trial-balance report.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Rillet data sources can also be manually configured to ingest data from any valid Rillet API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Rillet data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Rillet destination, and select the Send to Destination option from the menu. Select the Rillet connector from the list of available destination connectors, then select the credential that will be used to connect to Rillet, and click Next; or, create a new Rillet credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Rillet endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Customer

Create a new customer (AR). Each record from your Nexset is sent as a JSON request body to create one customer.

[Rest API] Create Vendor

Create a new vendor (AP). Each record from your Nexset is sent as a JSON request body to create one vendor.

[Rest API] Create Invoice

Create a new invoice (AR). Each record from your Nexset is sent as a JSON request body to create one invoice.

[Rest API] Create Bill

Create a new vendor bill (AP). Each record from your Nexset is sent as a JSON request body to create one bill.

[Rest API] Create Journal Entry

Create a new general-ledger journal entry. Each record from your Nexset is sent as a JSON request body to create one journal entry.

[Rest API] Create Credit Memo

Create a new AR credit memo. Each record from your Nexset is sent as a JSON request body to create one credit memo.

[Rest API] Create Product

Create a new product. Each record from your Nexset is sent as a JSON request body to create one product.

[Rest API] Create Charge

Create a new charge. Each record from your Nexset is sent as a JSON request body to create one charge.

[Rest API] Create Bank Transaction

Create a new bank transaction. Each record from your Nexset is sent as a JSON request body to create one bank transaction.

[Rest API] Create Contract

Create a new revenue contract. Each record from your Nexset is sent as a JSON request body to create one contract.

Manual configuration

Rillet destinations can also be manually configured to send data to any valid Rillet API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Rillet APIs expect JSON format for write operations. Ensure each record matches the structure that the target Rillet endpoint requires.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Rillet endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Rillet endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.