Skip to main content
POST
Split a manifest into a contract folder
POST https://api-datahub.octoparse.com/v1/data-apps/contract/split Authentication: none. Anonymous access allowed. Inverse of assemble: one self-contained manifest → a canonical contract-folder file map (each file is JSON text; zipping is the client’s job). Split semantics (single source of truth): platform-injected read-back keys (scope / status / namespace) are stripped; input / output each drop one schema wrapper and output.id_field moves back to the top level of output_schema.json; runtime / pricing / examples become standalone files whenever present; an empty README is omitted; remaining keys go into dataapp.json in original order. Re-assembling the split folder can reproduce the manifest with zero warnings. Optional translations ({source, locales}) additionally yields i18n.json.

Request

Request body

object
required
Manifest object.
object
Optional translation set {source, locales}.

Example request

Response

200 success

The payload is wrapped in data. Fields:
object
File map. Keys are filenames; values are JSON text.
string

Client libraries

The Python and JavaScript SDKs do not wrap this endpoint yet. Call REST directly.