back-office

Preview Release Notification

What announcing this release would create, without creating it (IBS-970).

The back office shows these counts for confirmation before firing. That confirmation is the only real guard against a mistyped version: notifications have no delete path, and a typo produces a different dedupe_key, so re-firing the correct version adds a second batch rather than replacing the bad one.

POST rather than GET because it shares the trigger's request body (and its validation) exactly; it writes nothing.

post/back-office/release-notifications/preview

Request

  • Base URL: https://api.incredibuild.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.incredibuild.com/back-office/release-notifications/preview
  • Auth: HTTP bearer

Headers

x-public-tenant-idstring uuid nullable
x-public-user-idstring uuid nullable

Request body

platform'windows' | 'linux' required
release_versionstring required

Response

Successful Response

grid_countinteger required
tenant_countinteger required
skipped_countinteger required
unparseable_version_countinteger required

Changes

No recorded changes to this operation across all 1 revision of this API.