Cursor

The platform reads your Cursor team members through the CursorAPI administrator so you can review who has access.

Attention

Use a team keyAPI(crsr_…) with Read-only area, created by a team administrator in the Cursor dashboard. User API Key will not It works because it cannot list team members through AdminAPI.

Prerequisites

• the platform organization administrator access
• The team administrator role in the Cursor (only team administrators can create and manage AdminAPI keys)
• A team of cursors on a paid system Business Plan (AdminAPI is not available for individual accounts)

Collected Fields

the platform field	Cursor field	Notes
Name	name	Member display name
Email	email	Member email address
Role	role	owner and free-owner map to Owner, member to Member, removed to Deleted; any other value goes through unchanged
Admin	role	It falls as an administrator when role is owner or free-owner
Status	isRemoved, role	Showing inactive when isRemoved is true or role is removed, otherwise active
MFA	Not supported
Last login	Not supported
External ID	id	Stable ID used to track your account through reviews
Created at	Not supported

Step 1: Create an API Key

1. In the cursor (signed as team administrator), open ___ZBT_I18N_RUNTIME_BLOCK_188__, go to Settings, and select API Keys in the sidebar.
2. Open the Team tab and click New API Key.
3. Enter a name (for example Probo Access Review), select a expiration date and set Scope to Read-only.
4. Create and copy the key (crsr_…), then save it securely.

Step 2: Connect in the platform

1. On the platform, go to Access Reviews > Sources > Add Source.
2. Find Cursor, click API KeyPut the key and click Connect.

AdministratorAPI does not expose any team or organization name endpoints, so the platform lists the source under the fixed Cursor name and attracts its members into your campaigns.

Troubleshooting

• Key rejected. Confirm that it is aAPIteam key (crsr_…) with Read-only A personal user key will not work and because the administrator only accepts basic Auth, Bearer tokens are rejected.
• No members appear. The key must be created by a team administrator and belong to the team you are reviewing on a paid business plan.