Ruddr is a professional services automation (PSA) platform for managing projects, clients, resourcing, time, expenses, and billing. The Nexla connector uses the Ruddr REST API to ingest data from your Ruddr workspace, including invoices, clients, projects, expenses, and workspace members, into any destination you configure.
Power end-to-end data operations for your Ruddr API with Nexla. Our bi-directional Ruddr connector is purpose-built for Ruddr, 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 Ruddr or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Ruddr 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 Ruddr credential in Nexla, you need a Ruddr API key. Ruddr authenticates API requests with a personal API key that is passed as a bearer token in the Authorization header of each request.
Open your workspace settings and navigate to the API Keys section.
Generate a new API key. Give it a descriptive name (e.g., "Nexla Integration") so it can be identified later.
Copy the API key value and store it securely, as it may not be retrievable after you leave the page.
The API key inherits the permissions of the account that created it, so ensure that account has access to the data you intend to ingest. If a key is compromised, revoke it in the API Keys section and generate a new one. For more information, see the Ruddr API Documentation.
After selecting the data source 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 Ruddr API key in the API Key field. This is the API key you generated in the API Keys section of your Ruddr workspace settings, as described in Prerequisites. Nexla sends this key as a bearer token in the Authorization header for all requests to the Ruddr API.
Your API key grants access to your Ruddr workspace data and should be treated as sensitive information. If the key is compromised, revoke it in the API Keys section of your Ruddr workspace settings and generate a new one.
For detailed information about authentication, available endpoints, and response formats, see the Ruddr 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 creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Ruddr connector tile, then select the credential that will be used to connect to your Ruddr workspace, and click Next; or, create a new Ruddr 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 Ruddr 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 Invoices
This endpoint template retrieves invoices from your Ruddr workspace. Use this template when you need to ingest invoices for reporting, analytics, or integration with other systems.
This endpoint issues a paginated GET request to https://www.ruddr.io/api/v1/invoices and returns all records accessible to your API key. Nexla automatically follows pagination to fetch subsequent pages until no further data is returned.
The response is returned in JSON format. Nexla organizes the retrieved invoices into one or more Nexsets that you can transform and route to any destination.
For details on response fields, pagination, and query parameters, see the Ruddr API Documentation.
[Rest API] List Clients
This endpoint template retrieves clients from your Ruddr workspace. Use this template when you need to ingest clients for reporting, analytics, or integration with other systems.
This endpoint issues a paginated GET request to https://www.ruddr.io/api/v1/clients and returns all records accessible to your API key. Nexla automatically follows pagination to fetch subsequent pages until no further data is returned.
The response is returned in JSON format. Nexla organizes the retrieved clients into one or more Nexsets that you can transform and route to any destination.
For details on response fields, pagination, and query parameters, see the Ruddr API Documentation.
[Rest API] List Project Members
This endpoint template retrieves project members from your Ruddr workspace. Use this template when you need to ingest project members for reporting, analytics, or integration with other systems.
This endpoint issues a paginated GET request to https://www.ruddr.io/api/v1/project-members and returns all records accessible to your API key. Nexla automatically follows pagination to fetch subsequent pages until no further data is returned.
The response is returned in JSON format. Nexla organizes the retrieved project members into one or more Nexsets that you can transform and route to any destination.
For details on response fields, pagination, and query parameters, see the Ruddr API Documentation.
[Rest API] List Workspace Members
This endpoint template retrieves workspace members from your Ruddr workspace. Use this template when you need to ingest workspace members for reporting, analytics, or integration with other systems.
This endpoint issues a paginated GET request to https://www.ruddr.io/api/v1/workspace-members and returns all records accessible to your API key. Nexla automatically follows pagination to fetch subsequent pages until no further data is returned.
The response is returned in JSON format. Nexla organizes the retrieved workspace members into one or more Nexsets that you can transform and route to any destination.
For details on response fields, pagination, and query parameters, see the Ruddr API Documentation.
[Rest API] List Projects
This endpoint template retrieves projects from your Ruddr workspace. Use this template when you need to ingest projects for reporting, analytics, or integration with other systems.
This endpoint issues a paginated GET request to https://www.ruddr.io/api/v1/projects and returns all records accessible to your API key. Nexla automatically follows pagination to fetch subsequent pages until no further data is returned.
The response is returned in JSON format. Nexla organizes the retrieved projects into one or more Nexsets that you can transform and route to any destination.
For details on response fields, pagination, and query parameters, see the Ruddr API Documentation.
[Rest API] List Project Tasks
This endpoint template retrieves project tasks from your Ruddr workspace. Use this template when you need to ingest project tasks for reporting, analytics, or integration with other systems.
This endpoint issues a paginated GET request to https://www.ruddr.io/api/v1/project-tasks and returns all records accessible to your API key. Nexla automatically follows pagination to fetch subsequent pages until no further data is returned.
The response is returned in JSON format. Nexla organizes the retrieved project tasks into one or more Nexsets that you can transform and route to any destination.
For details on response fields, pagination, and query parameters, see the Ruddr API Documentation.
[Rest API] List Expense Reports
This endpoint template retrieves expense reports from your Ruddr workspace. Use this template when you need to ingest expense reports for reporting, analytics, or integration with other systems.
This endpoint issues a paginated GET request to https://www.ruddr.io/api/v1/expense-reports and returns all records accessible to your API key. Nexla automatically follows pagination to fetch subsequent pages until no further data is returned.
The response is returned in JSON format. Nexla organizes the retrieved expense reports into one or more Nexsets that you can transform and route to any destination.
For details on response fields, pagination, and query parameters, see the Ruddr API Documentation.
[Rest API] List Expense Items
This endpoint template retrieves expense items from your Ruddr workspace. Use this template when you need to ingest expense items for reporting, analytics, or integration with other systems.
This endpoint issues a paginated GET request to https://www.ruddr.io/api/v1/expense-items and returns all records accessible to your API key. Nexla automatically follows pagination to fetch subsequent pages until no further data is returned.
The response is returned in JSON format. Nexla organizes the retrieved expense items into one or more Nexsets that you can transform and route to any destination.
For details on response fields, pagination, and query parameters, see the Ruddr API Documentation.
[Rest API] List Expense Categories
This endpoint template retrieves expense categories from your Ruddr workspace. Use this template when you need to ingest expense categories for reporting, analytics, or integration with other systems.
This endpoint issues a paginated GET request to https://www.ruddr.io/api/v1/expense-categories and returns all records accessible to your API key. Nexla automatically follows pagination to fetch subsequent pages until no further data is returned.
The response is returned in JSON format. Nexla organizes the retrieved expense categories into one or more Nexsets that you can transform and route to any destination.
For details on response fields, pagination, and query parameters, see the Ruddr API Documentation.
[Rest API] List Project Expense
This endpoint template retrieves project expense from your Ruddr workspace. Use this template when you need to ingest project expense for reporting, analytics, or integration with other systems.
This endpoint issues a paginated GET request to https://www.ruddr.io/api/v1/project-expenses and returns all records accessible to your API key. Nexla automatically follows pagination to fetch subsequent pages until no further data is returned.
The response is returned in JSON format. Nexla organizes the retrieved project expense into one or more Nexsets that you can transform and route to any destination.
For details on response fields, pagination, and query parameters, see the Ruddr API Documentation.
[Rest API] List Project Budget Expenses
This endpoint template retrieves project budget expenses from your Ruddr workspace. Use this template when you need to ingest project budget expenses for reporting, analytics, or integration with other systems.
This endpoint issues a paginated GET request to https://www.ruddr.io/api/v1/project-budget-expenses and returns all records accessible to your API key. Nexla automatically follows pagination to fetch subsequent pages until no further data is returned.
The response is returned in JSON format. Nexla organizes the retrieved project budget expenses into one or more Nexsets that you can transform and route to any destination.
For details on response fields, pagination, and query parameters, see the Ruddr API Documentation.
[Rest API] List Opportunity Stages
This endpoint template retrieves opportunity stages from your Ruddr workspace. Use this template when you need to ingest opportunity stages for reporting, analytics, or integration with other systems.
This endpoint issues a paginated GET request to https://www.ruddr.io/api/v1/opportunity-stages and returns all records accessible to your API key. Nexla automatically follows pagination to fetch subsequent pages until no further data is returned.
The response is returned in JSON format. Nexla organizes the retrieved opportunity stages into one or more Nexsets that you can transform and route to any destination.
For details on response fields, pagination, and query parameters, see the Ruddr API Documentation.
[Rest API] List Holidays
This endpoint template retrieves holidays from your Ruddr workspace. Use this template when you need to ingest holidays for reporting, analytics, or integration with other systems.
This endpoint issues a paginated GET request to https://www.ruddr.io/api/v1/holidays and returns all records accessible to your API key. Nexla automatically follows pagination to fetch subsequent pages until no further data is returned.
The response is returned in JSON format. Nexla organizes the retrieved holidays into one or more Nexsets that you can transform and route to any destination.
For details on response fields, pagination, and query parameters, see the Ruddr 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.
Ruddr data sources can also be manually configured to ingest data from any valid Ruddr 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 Ruddr 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.
