Cursor Administration Connector

Intro

This article explains how to use Domo’s Cursor Administration Connector to pull team administration data, including members, audit logs, usage metrics, spending, usage events, and billing groups.

Cursor is an AI-powered code editor that helps developers write, edit, and understand code more efficiently.

---

Prerequisites

To connect to the Cursor Administration API and create a DataSet, you need the Admin API Key associated with your Cursor account.

This article covers the fields and menus specific to the Cursor Administration Connector user interface. For general information about adding DataSets, setting update schedules, and editing DataSet information, see Add a DataSet Using a Data Connector.

Create an Admin API Key

1. Go to cursor.com/dashboard.
2. Navigate to Settings > Advanced > Admin API Keys.
3. Create a new Admin API key.
4. Copy the API key immediately after creation. The API key is displayed only once for security reasons.

Configure the Connection

This section describes the options in the Credentials and Details panes on the Cursor Administration Connector page. The components of the Scheduling and Name & Describe Your DataSet panes are universal across most connector types and are discussed in Add a DataSet Using a Data Connector.

Enter Your Credentials

The Credentials pane contains the field for entering credentials to connect to the Cursor Administration API. The following table describes what is needed for each field.

Field	Description
API Key	Enter the Admin API key associated with your Cursor account.

After you have entered valid credentials, you can use the same account any time you set up a new Domo-Cursor connection. You can manage connector accounts in the Accounts tab in the Data Center. For more information about this tab, see Manage User Accounts for Connectors.

Configure the Details Pane

This pane contains a primary Reports menu, along with various other menus for configuring your report.

Menu	Description
Report	Select the Cursor report you want to run. Team Members, Spending, and Billing Groups do not require a date range. Audit Logs, Daily Usage, and Usage Events require a date range. The following reports are available: Report Description Team Members Get the current list of users in your Cursor team, including account and role details. Audit Logs Get team audit activity events for the selected date range (up to 30 days per request). Daily Usage Get aggregated daily usage data for your team for the selected date range. Spending Get team spending and cost metrics (no date range required). Usage Events Get detailed usage event records for the selected date range. Billing Groups Get billing group definitions and related metadata for your team. Daily Usage (Partition) Get daily usage data using a partitioned incremental pattern with configurable backfill and restate windows. Usage Events (Partition) Get usage event records using a partitioned incremental pattern with configurable backfill and restate windows.
Date Range	Select a date range to retrieve the data. Audit Logs support a maximum range of 30 days.
Backfill Months	Specify the number of months to load on the first run. Defaults to 24.
Restate Months	Specify the number of recent months to refresh on each subsequent run. Defaults to 6. The value must be less than or equal to Backfill Months.

Configure Other Options

For information about the remaining sections of the connector interface, including how to configure scheduling, retry, and update options, see Add a DataSet Using a Data Connector.