Railz provides an Accounting Data as a Service API that aggregates financial, accounting, and banking data from a business's connected accounting platforms. Use the Railz connector to ingest normalized accounting data—such as invoices, bills, financial statements, and bank transactions—into Nexla, or to push records like invoices, bills, and journal entries back to connected businesses.
Power end-to-end data operations for your Railz API with Nexla. Our bi-directional Railz connector is purpose-built for Railz, 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 Railz or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Railz 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
Before creating a Railz credential, you need API credentials from your Railz account. Railz authenticates using a Client ID and Secret Key, which are exchanged for a short-lived access token that is then sent as a Bearer token in the Authorization header of each API request. All requests must be made over HTTPS.
To obtain your Railz API credentials, follow these steps:
Sign in to the Railz Dashboard using an account with Admin or Developer permissions.
Navigate to the Developers tab in the dashboard.
Locate your Client ID and Secret Key. These values identify your application and authenticate your API requests.
Copy the credential value required by Nexla and store it securely, as it grants access to your Railz account data.
Access tokens issued by Railz are valid for a limited time (60 minutes), so a fresh token is obtained as needed when making API calls. For detailed information about authentication and available endpoints, refer to the Railz API Documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Railz API key in the API Key Value field. This value is sent as a Bearer token in the Authorization header of each request to the Railz API and must be kept confidential.
If your API key is compromised, rotate your credentials in the Railz Dashboard under the Developers tab and update the credential in Nexla.
For detailed information about authentication and available endpoints, see the Railz API Documentation.
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.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Railz connector tile, then select the credential that will be used to connect to Railz, and click Next; or, create a new Railz credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Railz 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 Connections
Retrieve a list of all accounting/banking connections for the team.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] List Businesses
Retrieve a list of all businesses.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] List Business Info
Retrieve detailed information about connected businesses.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] List Accounts
Retrieve chart-of-accounts data for connected businesses.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] List Invoices
Retrieve invoices issued by connected businesses.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] List Bills
Retrieve bills owed by connected businesses.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] List Customers
Retrieve customers of connected businesses.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] List Vendors
Retrieve vendors of connected businesses.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] List Balance Sheets
Retrieve balance sheet financial statements.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] List Income Statements
Retrieve income statement financial statements.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] List Bank Accounts
Retrieve bank accounts linked to connected businesses.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] List Bank Transactions
Retrieve bank transactions for connected businesses.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] List Journal Entries
Retrieve journal entries recorded by connected businesses.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint.
Nexla handles pagination automatically, following the Railz API's paging to fetch all available records for the selected endpoint. For detailed information about request and response structures, see the Railz API Documentation.
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.
Railz data sources can also be manually configured to ingest data from any valid Railz 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 Railz 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.
Click the + icon on the Nexset that will be sent to the Railz destination, and select the Send to Destination option from the menu. Select the Railz connector from the list of available destination connectors, then select the credential that will be used to connect to Railz, and click Next; or, create a new Railz credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Railz 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 an Invoice
Create a new invoice for a connected business.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] Create a Bill
Create a new bill for a connected business.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] Create a Customer
Create a new customer for a connected business.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] Create a Vendor
Create a new vendor for a connected business.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] Create a Bank Account
Create a new bank account record for a connected business.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] Create a Journal Entry
Create a new journal entry for a connected business.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation. For detailed information about request and response structures, see the Railz API Documentation.
[Rest API] Disconnect a Connection
Disconnect an existing accounting/banking connection.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation.
Each record from your Nexset is sent as a separate API request to the Railz API. The request body should contain the data in the format required by the Railz API for this operation. For detailed information about request and response structures, see the Railz API Documentation.
Railz destinations can also be manually configured to send data to any valid Railz 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.
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 Railz endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Railz endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
