Overview
The Cursor integration lets administrators configure and manage Cursor API connections in G360. Once configured, these connections authenticate with Cursor services and enable integration with AI Coding Tools Metrics and reporting. Using this integration, administrators can:- Create Cursor connections and configure API credentials
- Associate Cursor projects
- Test connection validity
- Monitor connection status
- Manage existing Cursor integrations
Prerequisites
Before configuring the integration, ensure you have:- A Cursor Teams or Enterprise account
- Administrator access to your Cursor team
- A Cursor Admin API key (see Create a Cursor Admin API key)
Cursor Connections page
In G360, go to Integration → Cursor Connections. The page lists all configured Cursor integrations.Create a Cursor Admin API key
The API key authenticates requests between G360 and Cursor.1
Open the Cursor Dashboard
Sign in to your Cursor account and open the Cursor Dashboard.
2
Open the API Keys page
Navigate to the API Keys page.
3
Create the key
Click New API Key, enter a descriptive name such as
G360 Integration, and confirm the creation of the key.4
Copy the key
Copy the API key and store it securely.
Create a Cursor connection
1
Start a new connection
On the Cursor Connections page, click Add Connection. The Add Cursor Connection window opens.
2
Enter connection details
3
Test the connection
Click Test Connection and wait for validation to finish. If the API Key and Project ID are valid, the test succeeds. If it fails, review the configuration and retry.
4
Save the connection
Click Save Connection. The connection appears in the Cursor Connections list.
Manage connections
From the Cursor Connections page, you can view connection information, edit existing connections, and delete connections.Connection status
Monitor usage
The Last Used field shows the most recent time the connection was used. Use it to identify active integrations, detect unused connections, and review integration usage patterns.Troubleshooting
Connection test failed
Connection test failed
Possible causes
- Invalid API Key or Project ID
- Authentication failure
- Network connectivity issues
- Verify the API Key and Project ID.
- Confirm access to the Cursor project.
- Retry the connection test.
Connection shows as Inactive
Connection shows as Inactive
Possible causes
- Expired credentials or an invalid API Key
- Project access issues
- Verify the connection settings.
- Update the credentials if required.
- Re-test the connection.
Unable to save connection
Unable to save connection
Possible causes
- Missing required fields
- Failed validation
- Invalid configuration values
- Complete all required fields.
- Run a successful connection test.
- Save the connection again.
Best practices
- Use descriptive connection names to simplify administration and maintenance.
- Periodically validate API credentials.
- Remove unused connections.
- Review connection status and usage activity regularly.

