Publishing
Create release
Promote a ready build to a formal version. The version number is fixed at this moment.
POST
Create release
POST https://api-datahub.octoparse.com/v1/data-apps/{app_id}/releases
Authentication: API key required (Authorization: Bearer <API Key>). App author only; others get 404.
Promote a specified ready build to a formal version. The version number is fixed here: by default the patch segment of the current max version increments by one (first release is 0.1.0). An explicit version must be three numeric segments and strictly greater than the current max — use it for major or minor bumps.
Preconditions: the build exists and is ready; the snapshot is re-run through the validation pipeline (specs may have evolved while the build lived); if expected_revision is set, the workspace must not have concurrent edits. Concurrent publishes are arbitrated by the unique constraint on (publisher, app name, version); on auto-version conflicts the engine recomputes and retries once. After publish the workspace is kept — it may already be ahead of the released snapshot.
Request
Path parameters
string
required
App reference.
Request body
string
required
Build id to publish. Must be ready.
string
Explicit three-segment version. Omit to bump the patch segment.
integer
Expected current draft revision. Mismatch returns
409.Example request
Response
200 success
data. Fields:
string
required
—
string
—
string
required
Published version number.
string
required
Corresponding build.
string
Publish time.
string[]
—
Errors
Error responses use
{"error": {code, category, message, retryable}}. See Errors.