API Keys

Admins manage API keys from Settings -> API.

What API Keys Are For

Use API keys to:

Build custom integrations.
Sync users, clients, projects, assignments, actual hours, and time off.
Connect reporting workflows.
Automate safe operational updates.
Give approved tools limited access without sharing a personal login.

API keys can be full access or limited to the parts of Supervisible an integration needs. Choose the narrowest access that supports the workflow, such as read-only access for reporting or write access only for a trusted automation.

Operational Side Effects

API writes use the same project behavior as the app:

Updating project dates can notify subscribed users and mapped project Slack channels.
Updating project status can notify subscribers, recalculate update reminder schedules, and deliver the final completed or cancelled status change.
Creating, moving, or deleting assignments can update project team membership and shared project-channel team-change notifications.

Use a clear actor user for API keys so activity, notifications, and audit trails point back to the right automation owner.

Creating a Key

Go to Settings -> API.
Create a new key.
Choose a clear name, such as "Zapier Sync" or "Operations Export".
Select full access or the specific access areas the integration needs.
Choose an expiration, or leave the key without an expiration.
Copy the key when it is shown.

The token is shown once. If you lose it, revoke the key and create a replacement.

Managing Keys

The API page shows active keys, revoked keys, expired keys, key prefixes, who created each key, and when keys were last used. Revoke a key when an integration is retired, a token may have leaked, or an access pattern no longer needs API access.

Developer Reference

Technical setup details live in Developers. Use that reference when you or an integration partner are ready to connect an external system.