Height

Height was an autonomous project management and collaboration platform designed for product and engineering teams. It combined task tracking, real-time team chat, and AI-powered automation into a single workspace, allowing teams to manage backlogs, triage bugs, track sprints, and maintain live product documentation without manual overhead. Height supported multiple work views—including Kanban boards, Gantt charts, spreadsheet grids, and calendars—and used an AI engine to proactively handle administrative work such as backlog pruning, bug prioritization, and progress reporting. Its REST API provides programmatic access to workspace data including tasks, lists, activities, users, and field templates, enabling data ingestion and write-back integrations with external systems.

Power end-to-end data operations for your Height API with Nexla. Our bi-directional Height connector is purpose-built for Height, 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 Height or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Height 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

To connect Nexla to Height, you will need a Height API secret key. The Height API uses API key authentication — all requests are authenticated by passing your secret key in the Authorization request header using the format api-key <your-secret-key>.

Obtain a Height API Secret Key

Height API keys are personal access tokens tied to your Height user account and workspace. They are generated from within the Height application settings.

1. Sign in to your Height workspace at height.app.

2. Click your workspace name or avatar in the top-left corner to open the workspace menu.

3. Navigate to Settings in the workspace menu.

4. In the Settings panel, select the API section.

5. Your API secret key is displayed in the API section. Click Copy to copy the key to your clipboard.

   Height API keys are tied to your individual user account. Any API requests made using this key will be performed with the same permissions as your Height user account. Ensure the account used to generate the key has the appropriate access to the workspace resources you intend to read from or write to.

6. Store the copied secret key in a secure location. Treat it like a password — do not share it in publicly accessible code repositories or other unsecured environments.

Important

Height API keys provide full access to your Height workspace data on behalf of the associated user account. Rotate or revoke the key from Settings > API in Height if it is ever compromised or no longer needed.

For additional reference, see the Height API documentation.

Authenticate

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 Height API secret key obtained in Prerequisites in the Secret Key field. All requests to the Height API are made over HTTPS to the base URL https://api.height.app, and Nexla will include this key in the Authorization header of every request using the format api-key <your-secret-key>.

   The Height API enforces a rate limit of 120 requests per minute on most endpoints. Some endpoints, such as task creation and activity posting, have a stricter limit of 60 requests per minute. If your data flows generate a high volume of API calls, consider spacing out requests or using Nexla's scheduling options to stay within these limits. Requests that exceed the rate limit will receive a 429 Too Many Requests response.

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 and can be selected for use with a new data source or destination.

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 Height connector tile, then select the credential that will be used to connect to the Height workspace, and click Next; or, create a new Height 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 Height API 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; click on an endpoint to see more information about it and how to configure your data source for this endpoint.

Get Workspace

Retrieves the current workspace information, including the workspace name, ID, URL slug, and configuration details. Use this endpoint to obtain workspace-level metadata or to verify that your credential is connected to the correct Height workspace.

• This endpoint requires no additional configuration beyond selecting the template. Nexla will automatically retrieve the workspace record associated with the authenticated API key.
• The response includes the workspace ID, name, URL handle, and other workspace-level configuration data.

The workspace ID returned by this endpoint can be useful as a reference when building multi-step API calls or when joining Height data with records from other systems.

List Lists

Retrieves all lists shared with the entire workspace. In Height, lists are containers that organize tasks — similar to projects or boards in other tools. Use this endpoint to obtain list IDs and names, which are required when creating tasks or filtering task queries by list.

• This endpoint requires no additional configuration. Nexla will automatically retrieve all workspace-level lists accessible to the authenticated user.
• The response includes each list's unique ID, name, description, color, appearance, and other configuration attributes.
• Only lists shared with the entire workspace are returned. Private or restricted lists may not appear in the results depending on the authenticated user's permissions.

List IDs are required when using the Create Task or Search Tasks endpoints. Run this endpoint first to discover available list IDs if you intend to use them in other Height API calls.

Search Tasks

Searches for tasks within your Height workspace using a text query. Use this endpoint to retrieve tasks matching specific keywords, titles, or descriptions. This is particularly useful for building targeted data pipelines that pull only the tasks relevant to a specific project, team, or status.

• Enter your search query in the Query field. The query is matched against task titles and descriptions. For example:

  • Enter a keyword such as bug or release to find all tasks containing that term.
  • Enter a specific task title or partial title to locate a particular task.
  • Leave the query empty to retrieve all tasks in the workspace (subject to pagination limits).
• The response includes matching task records with their IDs, titles, descriptions, assignees, statuses, list assignments, due dates, and custom field values.

Height's search is performed across task titles and descriptions. For more targeted filtering (e.g., by status, assignee, or list), consider using the manual configuration option to construct a custom API request with specific query parameters.

List Users

Retrieves all users (workspace members) in your Height workspace. Use this endpoint to obtain user IDs, names, and email addresses for reporting, auditing, or cross-referencing with task assignee data.

• This endpoint requires no additional configuration. Nexla will automatically retrieve all user records from the workspace.
• The response includes each user's unique ID, display name, email address, and workspace role.
• User IDs returned by this endpoint correspond to the assignee and follower fields in task records, enabling joins between user and task data.

Use the user IDs from this endpoint to enrich task data with user details, such as mapping assignee IDs to names and email addresses for reporting dashboards or notifications.

List Field Templates

Retrieves all field templates defined in the workspace. Field templates define custom attributes that can be attached to tasks — such as priority levels, status options, labels, and numeric fields. Use this endpoint to discover available custom fields and their allowed values before creating or updating tasks with custom attribute data.

• This endpoint requires no additional configuration. Nexla will automatically retrieve all field template definitions from the workspace.
• The response includes each field template's unique ID, name, data type (e.g., select, multi-select, number, text, date), and the list of allowed values where applicable.
• Field template IDs and their allowed value IDs are required when creating tasks that include custom attribute values.

Running this endpoint is recommended before building task creation or update workflows, as it provides the full list of available custom fields and their valid values — ensuring that any custom attribute data you send to Height uses the correct IDs and formats.

List Activities

Retrieves activity records from your Height workspace. Activities represent events associated with tasks, including messages posted in task threads, status changes, assignment updates, and integration-related events (such as GitHub commits or pull request links). Use this endpoint to ingest collaboration history, audit task activity, or build activity feed integrations.

• Optionally, provide a Task ID to retrieve activities for a specific task. If no Task ID is provided, Nexla will retrieve activities across all tasks in the workspace.

  • Task IDs can be obtained by first running the Search Tasks endpoint.
• The response includes the activity type, the user who performed the action, the timestamp, and any associated content (e.g., message text or field change details).
• Activity types include: message (comments in task threads), createdTask, statusChange, assigneeChange, dueDateChange, and integration events such as GitHub PR links.

The Height API enforces a stricter rate limit of 60 requests per minute for activity-related endpoints. If your flow is retrieving activities for a large number of tasks, consider using Nexla's scheduling settings to pace the requests appropriately.

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

Height data sources can also be manually configured to ingest data from any valid Height 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.

Height API endpoints use the base URL https://api.height.app. Commonly used endpoints include /workspace, /lists, /tasks, /users, /fieldTemplates, and /activities — all read with GET, except the search endpoint (POST /tasks/search), which uses POST. All requests must use HTTPS, and the API enforces a rate limit of 120 requests per minute on most endpoints (60 requests per minute for activity and task creation endpoints).

Most Height list endpoints wrap their results in a top-level list property — for example, for the GET /lists endpoint, enter $.list[*] as the path to data to treat each list record as a separate row in the resulting Nexset. Date/time macros are useful for filtering Height results by date ranges, such as retrieving activities or tasks updated after a specific date using query parameters like updatedAt[gt] or createdAt[lt]. You do not need to include the Authorization header here — it is automatically applied by Nexla based on your Height credential configuration.

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 Height 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 Height destination, and select the Send to Destination option from the menu. Select the Height connector from the list of available destination connectors, then select the credential that will be used to connect to the Height workspace, and click Next; or, create a new Height 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 Height write operations. 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.

Create Task

Creates a new task in a specified Height list. Use this endpoint to programmatically populate your Height workspace with tasks generated from external systems — for example, creating Height tasks from bug reports, support tickets, form submissions, or data records from other tools.

• Enter the List ID of the Height list where the new task should be created. The list ID is required — tasks in Height must belong to a list. To find available list IDs, run the List Lists data source endpoint first and note the ID of the target list.

• Map the Task Name field to the Nexset attribute that contains the task title. Task names are required and should be concise and descriptive.

• Optionally, map additional task attributes from your Nexset to the corresponding Height task fields:

  • Description: A detailed description of the task, supporting plain text or markdown.
  • Assignees: One or more Height user IDs to assign the task to. User IDs can be obtained from the List Users endpoint.
  • Due Date: The task due date in ISO 8601 format (e.g., 2025-09-01T00:00:00.000Z).
  • Status: The initial task status. Must be a valid status value defined in your Height workspace.

The Height API enforces a rate limit of 60 requests per minute for the task creation endpoint (POST /tasks). If your data flow creates a large number of tasks, use Nexla's record batching or scheduling settings to stay within this limit and avoid 429 Too Many Requests errors.

Update Task

Updates an existing task in your Height workspace. Use this endpoint to synchronize task data from external systems — for example, updating task statuses, reassigning tasks, changing due dates, or modifying descriptions based on events in other tools.

• Enter the Task ID of the Height task to be updated in the destination URL. Task IDs are unique identifiers that can be obtained by running the Search Tasks data source endpoint.

• Map the fields you want to update from your Nexset to the corresponding Height task attributes. Only the fields you include in the request will be updated — existing values for omitted fields will remain unchanged:

  • Name: The updated task title.
  • Description: The updated task description.
  • Status: The updated task status. Must match a valid status option in your Height workspace.
  • Assignees: Updated list of assignee user IDs. Providing an empty array removes all assignees.
  • Due Date: The updated due date in ISO 8601 format.

Height task updates are performed using PATCH /tasks/{'{taskId}'}. Include only the fields you want to change in the request body — Height uses a partial update (patch) model, so unspecified fields are not modified.

Post Activity (Task Comment)

Posts a new activity (message or comment) to a Height task's activity thread. Use this endpoint to add contextual updates, notifications, or status messages to Height tasks from external systems — for example, appending deployment statuses, system alerts, or automated progress updates to relevant tasks.

• Enter the Task ID of the Height task to which the activity should be posted. Task IDs can be obtained using the Search Tasks data source endpoint.
• Map the Message field to the Nexset attribute containing the comment text. The message supports plain text content.
• The activity will appear in the task's comment thread and will be attributed to the Height user associated with the API key used for authentication.

The Height API enforces a rate limit of 60 requests per minute for the activity creation endpoint (POST /activities). If your flow generates a high volume of comments, use Nexla's scheduling settings to pace requests within this limit.

Manual configuration

Height destinations can also be manually configured to send data to any valid Height 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.

Height's REST API accepts JSON-formatted request bodies — select JSON as the content format. Height API endpoints use the base URL https://api.height.app; commonly used destination endpoints include POST /tasks (create a task), PATCH /tasks/{'{taskId}'} (update a task, replacing {'{taskId}'} with the task's unique ID), and POST /activities (post an activity or comment). For update operations, include the task ID at the end of the URL path (e.g., https://api.height.app/tasks/task-id-here).

The Height API processes individual task and activity records per request and does not natively support bulk creation of multiple records in a single call — for most Height write operations, a batch size of 1 (one record per request) is recommended to maintain compatibility with the API's single-record model. Common write endpoints are rate-limited to 60 requests per minute. You do not need to include the Authorization header here — it is automatically applied by Nexla based on your Height credential configuration. Enabling the response webhook option lets you capture the response from each call — for example, the newly created task's ID and details — into a new Nexla webhook data source.

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 Height endpoint, open the destination resource menu, and select Activate.

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