API keys and authentication

Create, store, rotate, and revoke scoped Patvero workspace API keys safely.

Authenticate a request

Send the complete key using one of the supported headers.

Bearer tokenhttp

Authorization: Bearer pv_live_your_secret

Alternative headerhttp

X-Patvero-API-Key: pv_live_your_secret

Server-side only

A key authorizes access to workspace data within its scopes. Do not embed it in a frontend bundle, desktop package, mobile build, or public request.

Each integration endpoint requires its matching permission.

workspace.read — workspace identity and metadata.
members.read — active workspace member summaries.
meetings.read — workspace meeting summaries.
meetings.write — create scheduled meetings, send invitations, and receive the join link.
projects.read — workspace-visible project summaries.

The key list shows metadata and the secret prefix, never the complete secret.

1
Create
Choose a unique name, scopes, and optional expiry.
2
Store
Save the one-time secret in a managed secret store.
3
Test
Use Test key in Patvero or call the workspace endpoint from your server.
4
Change permissions
Use Permissions beside an active key. Patvero applies the new scopes immediately without changing the secret already stored by your integration.
5
Rotate
Generate a replacement, update the consumer, verify it, then remove the old secret from your systems.
6
Revoke
Revoke immediately when access ends or exposure is suspected. Revocation cannot be undone.

KEEP EXPLORING

Connect trusted systems to Patvero using scoped workspace API keys and the versioned REST API.

Read workspace data and securely create scheduled meetings through the scoped integration API.

Protect identities, media, records, integrations, and administrative actions across Patvero.

Was this guide useful?

Tell us what was missing and include the page title.