Add a release to the product's default variant (member)
const url = 'https://example.com/v1/orgs/example/products/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/releases';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"version":"example","released_at":"2026-04-15T12:00:00Z"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/v1/orgs/example/products/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/releases \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "version": "example", "released_at": "2026-04-15T12:00:00Z" }'For products with a single build. The release goes into the variant named
default, which is created if the product has none.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Organization (tenant) slug, e.g. alpenrobotik
Request Bodyrequired
Section titled “Request Bodyrequired”object
Unique within the default variant
Example generated
{ "version": "example", "released_at": "2026-04-15T12:00:00Z"}Responses
Section titled “Responses”Created
object
Example generated
{ "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "variant_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "version": "example", "released_at": "2026-04-15T12:00:00Z", "created_at": "2026-04-15T12:00:00Z"}The version is missing
Role below member
No such object in this organization, no such organization, or the caller does not belong to it
This version exists in the default variant
Over the operation’s rate-limit budget (x-affectra-budget): code request.rateLimited with params.budget. Wait Retry-After seconds before trying again.
Every error answer, Content-Type
application/problem+json. The web app and integrations translate code; detail is English,
for people reading curl output or CI logs, and may change wording at
any time. Match on code, never on detail.
object
The HTTP status
Stable error codes. A code is never renamed; new ones may be added, so
a client falls back to detail for a code it doesn’t know. Another
organization’s object answers notFound, the same as a missing one.
What went wrong
Values the code’s message needs, e.g. {“field”: “version”}. Only values the caller sent or may see. Empty when the message needs none.
object
Example
{ "code": "notFound"}Headers
Section titled “Headers”Seconds until a request would be allowed again, at least 1