Release API

Tells Nohmo a version shipped, so metric movements can be attributed to it. Call it from CI after a deploy. The SDK also reports releases automatically, so this is only needed when you want CI to be the source of truth or to add a commit SHA and release notes.

POST /api/tracker/release/

bash

curl -X POST https://www.nohmo.in/api/tracker/release/ \
  -H "Content-Type: application/json" \
  -H "X-API-Key: pk_xxxx" \
  -d '{
    "version": "2.4.1",
    "platform": "ios",
    "name": "Checkout rewrite",
    "commitSha": "9f2c1ab",
    "releasedAt": "2026-08-23T10:00:00Z"
  }'

Field	Required	Description
version	✓	Version string, max 100 characters
platform	—	web, ios, android, or blank for all surfaces
name	—	Human label for the release, max 255 characters
commitSha	—	Commit SHA, max 64 characters
releasedAt	—	ISO-8601 datetime. Defaults to now
environment	—	Defaults to production
notes	—	Free-text release notes

Response

json

{
  "success": true,
  "data": {
    "id": "6f1e...",
    "version": "2.4.1",
    "platform": "ios",
    "releasedAt": "2026-08-23T10:00:00+00:00",
    "source": "api",
    "created": true
  }
}

Note: Returns 201 when the release is new and 200 when it already existed, so re-running a deploy job is safe. A release the SDK auto-detected is upgraded to source: "api" when CI reports the same version.

Status	Meaning
400	Invalid JSON, version missing, bad platform, or releasedAt not ISO-8601
401	API key missing or invalid