Skip to main content
Configure a project before deploying, running jobs, or connecting integrations.

​
Steps

  1. Create or select a project.
  2. Apply a template when the project needs starter resources.
  3. Create environments for development, preview, or production.
  4. Add variables and secrets for each environment.
  5. Review configuration before deployment or runtime work.

​
Try it with REST

Create a project: POST /projects
Terminal
curl -X POST https://api.veryfront.com/projects \
  -H "Authorization: Bearer $VERYFRONT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Support Assistant",
    "slug": "support-assistant",
    "templateSlug": "blank"
  }'
Create a production environment: POST /projects/{project_reference}/environments
Terminal
curl -X POST https://api.veryfront.com/projects/support-assistant/environments \
  -H "Authorization: Bearer $VERYFRONT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "production"
  }'

​
API surfaces

SurfaceStart here
RESTProjects, Create Project, Environments
GraphQLCreate Project, Create Environment
MCPCreate Project, Create Environment

​
Verify

List projects and confirm the project slug exists. List environments and confirm production exists for the project.

​
Configuration surfaces

SurfaceUse it for
ProjectResource ownership, source, access, logs, and usage.
TemplateStarter structure for a project.
EnvironmentVariables, secrets, domains, and deployment targets.

​
API reference

APIUse
RESTProjects, templates, and environments.
GraphQLProject and environment views.
MCPProject, template, and environment tools.