Rocketlane is a customer onboarding and project management platform for professional services teams. Its REST API lets you manage projects, tasks, phases, placeholders, and time entries programmatically. Nexla connects to the Rocketlane API to ingest this data into your pipelines and to push updates back into Rocketlane.
Power end-to-end data operations for your Rocketlane API with Nexla. Our bi-directional Rocketlane connector is purpose-built for Rocketlane, 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 Rocketlane or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Rocketlane 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 Rocketlane credential, you need an API key from your Rocketlane account. Rocketlane authenticates every API request with a secret token that is sent in the api-key request header.
To generate a Rocketlane API key, follow these steps:
Sign in to your Rocketlane account.
Select your profile icon in the vertical navigation bar on the left, then select Settings.
Open Settings > API (the developer console).
Generate a new API key.
Copy the API key value and store it securely. You will need it to configure your Nexla credential.
Treat the API key like a password and keep it confidential. For security, periodically review the API keys you have created and deauthorize any that are no longer needed. If a key is compromised, deauthorize it in the API section of your Rocketlane settings and generate a new one. For more detail, see the Rocketlane 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 Rocketlane API key in the API Key Value field. This is the key you generated in Prerequisites, and it is sent in the api-key header for all API requests to the Rocketlane API. This value is stored securely and must be kept confidential.
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 Rocketlane connector tile, then select the credential that will be used to connect to the Rocketlane instance, and click Next; or, create a new Rocketlane 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 Rocketlane 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] Get all projects
Get all projects. This endpoint template retrieves the list of projects in your Rocketlane account.
Optional query parameters let you narrow and page through the results: pagesize and pagetoken control pagination, and status filters projects by their status.
For detailed information about project fields, filtering, and response structures, see the Rocketlane API documentation.
[Rest API] Get project by Id
Get project by Id. This endpoint template retrieves a single project by its identifier.
Provide the projectid path parameter to identify the project to fetch.
Get all tasks. This endpoint template retrieves the list of tasks in your Rocketlane account.
Optional query parameters let you scope and page through the results: projectid filters tasks to a single project, status filters by task status, and pagesize and pagetoken control pagination.
For detailed information about task fields, filtering, and response structures, see the Rocketlane API documentation.
[Rest API] Get task by Id
Get task by Id. This endpoint template retrieves a single task by its identifier.
Provide the taskid path parameter to identify the task to fetch.
Get all time entries. This endpoint template retrieves logged time entries from your Rocketlane account.
Optional query parameters let you scope the results: projectid filters time entries to a single project, and userid filters them to a single user.
For detailed information about time entry fields, filtering, and response structures, see the Rocketlane 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.
Rocketlane data sources can also be manually configured to ingest data from any valid Rocketlane 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 Rocketlane 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 Rocketlane destination, and select the Send to Destination option from the menu. Select the Rocketlane connector from the list of available destination connectors, then select the credential that will be used to connect to the Rocketlane account, and click Next; or, create a new Rocketlane credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Rocketlane 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 a project
Create a project. This endpoint template creates a new project in Rocketlane using records from a Nexset.
Each record from your Nexset is sent as JSON in the request body to create a new project. The record must match the structure the Rocketlane API expects for project creation.
For detailed information about the request body format and required fields, see the Rocketlane API documentation.
[Rest API] Update project by Id
Update project by Id. This endpoint template updates an existing project.
Provide the projectid path parameter to identify the project to update. Each record from your Nexset is sent as JSON in the request body with the fields to change.
For detailed information about the request body format and updatable fields, see the Rocketlane API documentation.
[Rest API] Delete project by Id
Delete project by Id. This endpoint template deletes a project.
Provide the projectid path parameter to identify the project to delete.
Add members to a project. This endpoint template adds one or more members to a project.
Provide the projectid path parameter to identify the project. Each record from your Nexset is sent as JSON in the request body identifying the members to add.
Remove members from a project. This endpoint template removes one or more members from a project.
Provide the projectid path parameter to identify the project. Each record from your Nexset is sent as JSON in the request body identifying the members to remove.
[Rest API] Assign placeholder to a user in a project
Assign placeholder to a user in a project. This endpoint template assigns a project placeholder to a user.
Provide the projectid path parameter to identify the project. Each record from your Nexset is sent as JSON in the request body identifying the placeholder and the user to assign it to.
[Rest API] Unassign placeholder from a user in a project
Unassign placeholder from a user in a project. This endpoint template removes a placeholder assignment from a user.
Provide the projectid path parameter to identify the project. Each record from your Nexset is sent as JSON in the request body identifying the placeholder to unassign.
Import a template to a project. This endpoint template imports a project template into an existing project.
Provide the projectid path parameter to identify the target project. Each record from your Nexset is sent as JSON in the request body identifying the template to import.
Create a task. This endpoint template creates a new task in Rocketlane using records from a Nexset.
Each record from your Nexset is sent as JSON in the request body to create a new task. The record must match the structure the Rocketlane API expects for task creation.
For detailed information about the request body format and required fields, see the Rocketlane API documentation.
[Rest API] Update task by Id
Update task by Id. This endpoint template updates an existing task.
Provide the taskid path parameter to identify the task to update. Each record from your Nexset is sent as JSON in the request body with the fields to change.
For detailed information about the request body format and updatable fields, see the Rocketlane API documentation.
[Rest API] Delete task by Id
Delete task by Id. This endpoint template deletes a task.
Provide the taskid path parameter to identify the task to delete.
Add assignees to a task by Id. This endpoint template adds one or more assignees to a task.
Provide the taskid path parameter to identify the task. Each record from your Nexset is sent as JSON in the request body identifying the assignees to add.
Remove assignees from a task by Id. This endpoint template removes one or more assignees from a task.
Provide the taskid path parameter to identify the task. Each record from your Nexset is sent as JSON in the request body identifying the assignees to remove.
Add followers to a task by Id. This endpoint template adds one or more followers to a task.
Provide the taskid path parameter to identify the task. Each record from your Nexset is sent as JSON in the request body identifying the followers to add.
Remove followers from a task by Id. This endpoint template removes one or more followers from a task.
Provide the taskid path parameter to identify the task. Each record from your Nexset is sent as JSON in the request body identifying the followers to remove.
Add dependencies to a task by Id. This endpoint template adds one or more dependencies to a task.
Provide the taskid path parameter to identify the task. Each record from your Nexset is sent as JSON in the request body identifying the dependencies to add.
Remove dependencies from a task by Id. This endpoint template removes one or more dependencies from a task.
Provide the taskid path parameter to identify the task. Each record from your Nexset is sent as JSON in the request body identifying the dependencies to remove.
Move a task to a phase by Id. This endpoint template moves a task into a different phase.
Provide the taskid path parameter to identify the task. Each record from your Nexset is sent as JSON in the request body identifying the destination phase.
Create a phase. This endpoint template creates a new phase in Rocketlane using records from a Nexset.
Each record from your Nexset is sent as JSON in the request body to create a new phase. The record must match the structure the Rocketlane API expects for phase creation.
For detailed information about the request body format and required fields, see the Rocketlane API documentation.
[Rest API] Update phase by Id
Update phase by Id. This endpoint template updates an existing phase.
Provide the phaseid path parameter to identify the phase to update. Each record from your Nexset is sent as JSON in the request body with the fields to change.
For detailed information about the request body format and updatable fields, see the Rocketlane API documentation.
[Rest API] Delete phase by Id
Delete phase by Id. This endpoint template deletes a phase.
Provide the phaseid path parameter to identify the phase to delete.
Rocketlane destinations can also be manually configured to send data to any valid Rocketlane 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.
Rocketlane APIs expect JSON format for write operations. For update, delete, archive, and other operations that act on a specific record, include the ID of the object at the end of the URL.
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 Rocketlane endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Rocketlane endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
