Publishing
Rename data app
Change the app name (routing alias) without releasing a version or affecting in-flight runs.
POST
Rename data app
POST https://api-datahub.octoparse.com/v1/data-apps/{app_id}/rename
Authentication: API key required (Authorization: Bearer <API Key>). App author only; others get 404.
Rename is fully open — not limited to zero-release apps. The app name is a routing alias: rename does not publish a version, does not invalidate old versions, and does not affect in-flight runs (all durable references pin app_id).
Broken caller references are the developer’s responsibility: old owner/old-name references (MCP pins, SDKs, REST, detail URLs) return a clean 404 after rename with no redirect. Historical runs and billing show the new name. The old name is not claimable by others in your namespace, but you can reuse it later for a new app — residual external references would then point at the new app. Consumers should integrate by app_id.
Validation matches create-identity: naming rules → reserved words → new name ≠ current name. Conflict with someone else’s historical binding is 409 app-name-reserved; conflict with another of your apps is 409 app-name-taken.
Request
Path parameters
string
required
App reference.
Request body
string
required
—
Example request
Response
200 success
data. Fields:
string
required
Stable app id — unchanged.
string
required
New name.
string
Publisher username.
Errors
Error responses use
{"error": {code, category, message, retryable}}. See Errors.