Skip to main content
Manage access before users, services, or integrations run project work.

​
Steps

  1. Create API keys for trusted services.
  2. Invite users who need project access.
  3. Connect OAuth providers for user-authorized integrations.
  4. Review access before running work in a project.

​
Try it with REST

List active API keys: GET /api-keys?status=active
Terminal
curl "https://api.veryfront.com/api-keys?status=active" \
  -H "Authorization: Bearer $VERYFRONT_API_KEY"
Create a server-side key: POST /api-keys
Terminal
curl -X POST https://api.veryfront.com/api-keys \
  -H "Authorization: Bearer $VERYFRONT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "CI key"
  }'

​
API surfaces

SurfaceStart here
RESTAPI Keys, OAuth, REST overview
GraphQLAPI Keys, Create API Key
MCPList API Keys, Create API Key

​
Verify

Confirm the current user has access to the target project. Rotate or delete keys that no trusted client uses.

​
Access surfaces

SurfaceUse it for
API keysTrusted server-side clients and MCP clients.
Project membersHuman access to project resources.
OAuth connectionsUser or workspace authorization for integrations.

​
API reference

APIUse
RESTAPI keys, OAuth, users, project users, and favorites.
GraphQLUser and member views.
MCPUser, member, API key, and favorite tools.