About Cerby
Cerby is an identity, access, and password management platform for “disconnected” applications: apps without SSO/SCIM support or with seat-based licensing in social/marketing tools. Connecting Cerby to Serval enables centralized lifecycle management of those accounts, automated user provisioning into business hub integrations, and password/secret reads from Cerby-managed vaults.What the Cerby integration enables
| Capability | Description |
|---|---|
| Account inventory | List accounts, retrieve account metadata, and inspect MFA/rotation state |
| Secret reads | Read passwords and TOTP codes for accounts stored in supported vaults |
| User & team management | List users and teams, create local/guest users, share accounts and collections |
| Business hub integrations | List, invite, update entitlements for, and remove users from connected SaaS integrations |
| Job monitoring | Poll automated job status (e.g. invite-user, update-entitlement) until completion |
Cerby configuration
Prerequisites
- An active Cerby workspace
- Workspace Admin, Super Admin, or Owner role (required for most read endpoints and all write endpoints)
- Permission to create API keys in the Cerby web app
Create an API key
Select scopes
Grant the scopes you intend to use from Serval. The minimum set the healthchecks exercise is:
- Read accounts
- Read users
- Read items (collections / secrets)
- Read integrations
- Read vaults
Identify your workspace name
Your Cerby workspace name is the subdomain in your URL. Forhttps://acme.cerby.com, the workspace name is acme. Serval uses it to build the base host acme.cerby.com for every API call.
Serval configuration
- In Serval, go to Apps → Available → Cerby → Connect
-
Enter the following:
Field Description Workspace name The subdomain part of your Cerby URL (e.g., acmeforacme.cerby.com). Do not include.cerby.com.API Token The API key created above - Click Save
Serval will verify your credentials and connect to Cerby. Once saved, run the healthchecks below to confirm each required scope is present.
Healthchecks
The Cerby integration ships with five read-only healthchecks. Each exercises a different scope so a failure tells you exactly which permission is missing.| # | Healthcheck | Scope required |
|---|---|---|
| 001 | Validate API connection | Read vaults |
| 002 | List users | Read users |
| 003 | List teams | Read users (also needs Admin role) |
| 004 | List integrations | Read integrations |
| 005 | List collections | Read items |
Additional resources
Cerby API documentation
Full API reference for the Cerby platform
Cerby
Learn more about Cerby’s identity and access management platform
Need help? Contact support@serval.com for assistance with your Cerby integration.

