Setting the file. One moment.
Subchapter 8.4
references/management-api.mdMarkdown3 KBView on GitHub
Use Prisma Management API for programmatic provisioning and workspace/project/database management.
CRITICAL
When you need backend automation, multi-tenant onboarding flows, or controlled resource provisioning, the Management API is the source of truth and is more reliable than interactive workflows.
https://api.prisma.io/v1https://api.prisma.io/v1/dochttps://api.prisma.io/v1/swagger-editorAuthorization: Bearer $TOKENhttps://auth.prisma.io/authorize with client_id, redirect_uri, response_type=code, and scopes.code on callback.https://auth.prisma.io/token.Workspace -> Project -> Branch -> Database. Branches are a first-class resource: databases attach to a Branch, and branch-scoped env/databases are how preview isolation works.
The 1.55 OpenAPI surface includes:
App/deployment, branch mutation, SCM, and bucket routes include experimental surfaces. Read the installed SDK types or live OpenAPI before building durable automation around them.
Connection create/rotate responses reveal credentials once. Later reads redact or omit the secret, so store the URL immediately. Use the structured direct/pooled endpoint returned by the concrete operation; do not assume a historical flat response shape.
Workspace service-token creation also returns the complete token value exactly once. List calls expose only metadata and a valueHint; delete revokes the token. Keep workspace and token ids opaque, and never log a create response.
Database create supports explicit project, region, branch, and source context. A source may be empty, a backup, or another database. Backup records are incremental; rely on current fields and documented units rather than old full-backup examples.