Applications

Fork Application Variant

Changed on

Fork an existing variant into a new variant on the same application.

Use this to experiment without touching the source variant's history. The fork copies the source variant's revisions up to the specified revision (or tip) into the new variant, then commits the supplied revision object on top. Both variant and revision sub-objects in the request must be present; the server returns count: 0 when either is missing. Returns 400 Bad Request if the fork target is invalid (for example, the source variant or revision cannot be located in this application's lineage).

post/applications/variants/fork

Request

  • Base URL
    /api (relative, and the document was published on a file host, not at the API’s origin)
  • URL
    /api/applications/variants/fork
  • Auth
    API key in header Authorization

Query parameters

application_variant_idstring uuid nullable

Request body

Response

Successful Response

countinteger

1 when a variant was found, 0 otherwise.

Changes

  • 5a14788d939fRevision changes
    • breaking

      added the new required request property

    • breaking

      added the new required request property

    • warning

      removed the request property

    • info

      added the new optional request property

  • 2040366204e5Revision changes
    • info

      added the optional property // to the response with the status

    • info

      added the optional property // to the response with the status

    • info

      added the optional property // to the response with the status