Endpoint
Request
Headers
Must be
application/jsonBody Parameters
The Git repository URL to clone and deploy. Supports HTTPS Git URLs.Example:
https://github.com/username/repository.gitResponse
Success Response
Always
true when the deployment is successfully initiatedA unique deployment identifier. Use this ID to reference your deployment.Example:
abc123def456Error Response
Error message describing what went wrong
Status Codes
- 200 - Deployment successfully queued
- 500 - Failed to clone repository (invalid URL, network issues, or private repository)
Examples
Response Examples
Successful Deployment
Error Response
What Happens After Upload
- The repository is cloned to the server
- All files are uploaded to S3 storage with the deployment ID
- The deployment ID is added to a build queue
- A build worker processes the deployment asynchronously
The endpoint returns immediately after queueing the deployment. The actual build process happens asynchronously. See Deployment Status for tracking your deployment.
Common Errors
| Error | Cause | Solution |
|---|---|---|
| Failed to clone repository | Invalid Git URL | Verify the repository URL is correct and accessible |
| Failed to clone repository | Private repository | Ensure the repository is public or configure authentication |
| Failed to clone repository | Network timeout | Check network connectivity and try again |
| 400 Bad Request | Missing url field | Include url in the request body |