Skip to main content
POST
/
releases
curl -X POST "https://kodostatus.com/api/v1/releases" \
  -H "X-API-Key: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "version": "1.2.3",
    "service_id": "svc_abc123",
    "environment": "production",
    "commit_sha": "a1b2c3d4e5f6g7h8",
    "repository": "https://github.com/org/repo"
  }'

{
  "id": "rel_abc123",
  "version": "1.2.3",
  "service_id": "svc_abc123",
  "environment": "production",
  "deployed_at": "2024-01-15T10:00:00Z",
  "commit_sha": "a1b2c3d4e5f6g7h8",
  "repository": "https://github.com/org/repo",
  "deployed_by": null,
  "error_count": 0,
  "new_errors": 0,
  "regressed_errors": 0
}
Tracking releases allows Kodo to:
  • Correlate errors with specific deployments
  • Detect regressions (previously resolved errors reappearing)
  • Show error trends across versions
  • Identify which deploy introduced new issues

​
Request Body

​
version
string
required
Semantic version or release identifier (e.g., “1.2.3”, “2024-01-15-abc”)
​
service_id
string
required
The service this release belongs to
​
environment
string
default:"production"
Deployment environment: production, staging, development
​
commit_sha
string
Git commit SHA for this release
​
repository
string
Repository URL for linking to commits
​
deployed_by
string
User or system that triggered the deploy

​
Response

Returns the created release object. 
curl -X POST "https://kodostatus.com/api/v1/releases" \
  -H "X-API-Key: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "version": "1.2.3",
    "service_id": "svc_abc123",
    "environment": "production",
    "commit_sha": "a1b2c3d4e5f6g7h8",
    "repository": "https://github.com/org/repo"
  }'

{
  "id": "rel_abc123",
  "version": "1.2.3",
  "service_id": "svc_abc123",
  "environment": "production",
  "deployed_at": "2024-01-15T10:00:00Z",
  "commit_sha": "a1b2c3d4e5f6g7h8",
  "repository": "https://github.com/org/repo",
  "deployed_by": null,
  "error_count": 0,
  "new_errors": 0,
  "regressed_errors": 0
}
Add release tracking to your CI/CD pipeline to automatically correlate errors with deployments. This makes it easy to identify which deploy introduced issues.