Deploy a project

Create a release from project source, then deploy that release to an environment. You need a configured project, an environment, and an API credential authorized to deploy. Replace support-assistant with your project reference and keep the environment’s UUID available.

1. Create a release

Create a release with POST /projects/{project_reference}/releases:

create-release.sh

curl -X POST https://api.veryfront.com/projects/support-assistant/releases \
  -H "Authorization: Bearer $VERYFRONT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Production release"}'

When branch_reference is omitted, the release uses the main branch. Set that field to a branch ID or name to release another branch.

2. Inspect the release

Set RELEASE_ID to the created release’s ID and read GET /projects/{project_reference}/releases/{release_id}:

read-release.sh

export RELEASE_ID="<RELEASE_ID>"
curl --fail-with-body "https://api.veryfront.com/projects/support-assistant/releases/$RELEASE_ID" \
  -H "Authorization: Bearer $VERYFRONT_API_KEY"

Review the recorded build state and assets before deploying. The release reference describes build and asset-manifest operations.

3. Deploy the release

Deploy the release with POST /projects/{project_reference}/deployments. Replace both UUID placeholders with values returned for your project.

create-deployment.sh

curl -X POST https://api.veryfront.com/projects/support-assistant/deployments \
  -H "Authorization: Bearer $VERYFRONT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"release_id":"<RELEASE_ID>","environment_id":"<ENVIRONMENT_ID>"}'

Verify the result

Set DEPLOYMENT_ID to the returned deployment ID, then read GET /projects/{project_reference}/deployments/{deployment_id}:

read-deployment.sh

export DEPLOYMENT_ID="<DEPLOYMENT_ID>"
curl --fail-with-body "https://api.veryfront.com/projects/support-assistant/deployments/$DEPLOYMENT_ID" \
  -H "Authorization: Bearer $VERYFRONT_API_KEY"

Confirm the release and environment IDs match the requested deployment. Then check the application’s configured endpoint. Inspect logs and traces if it fails to serve requests. Creating a release does not deploy it. To serve another release, create a new deployment; the existing deployment’s release and environment are fixed.

API references

Interface	Operations
REST	Create a release · Create a deployment
GraphQL	Create a release · Create a deployment
MCP	Create a release · Create a deployment

Get started

APIs

REST API

GraphQL API

MCP API

1. Create a release

2. Inspect the release

3. Deploy the release

Verify the result

API references

​1. Create a release

​2. Inspect the release

​3. Deploy the release

​Verify the result

​API references

1. Create a release

2. Inspect the release

3. Deploy the release

Verify the result

API references