Prerequisites
- A platform API key with a client ID (
plt-…) and a client secret (abl_…). - A project ID that’s in the key’s allowed projects.
- The
cicd.release.create,cicd.deploy, andcicd.promotescopes on the key. - Authority on each environment you deploy or promote to. Call Get caller identity to check.
Endpoints
Workflow
To deploy content from another workspace, first move it into the target project with the project import and export API. Then build the release from a project snapshot.- Exchange the platform API key for a Bearer token. Send the token in the
Authorization: Bearer <token>header on every other call. The token expires after 900 seconds by default. - Call
whoamito confirm the environments you can deploy and promote to. - Create a release. Use
source.kind="project_snapshot"to build from the project’s current content, orgitto build from a branch, tag, or commit. - Poll the release until its status is
ready. - Create a deployment with the
releaseIdand a target environment:dev,staging, orproduction. - Poll the deployment until its status is
active. - Promote the active deployment to a higher environment.
Behavior to know
- A release is immutable and independent of the environment. Promotion moves the same release to the target environment.
- Release builds, deployments, and promotions run asynchronously. Use the status endpoints to track them.
- The API checks environment authority at deploy and promote time, not when you build a release.
- A qualification gate runs on every deploy and promote. To bypass it, set
bypassQualificationGateandbypassReason. The key needs thecicd.gate.bypassscope.