# Clone Workset This API will create a copy of the workset with the new name specified in the API call. It is run as a POST call and adds a variable for the new workset name to the call used to get workset details (ie, after 'workset' the API includes the instruction 'clone' and then the ID of the workset being cloned and the name of the new workset being created). The API looks like the example below. https\://\:\/core/API/workSet/clone/\?name=\. For example, it would be: . When creating this url, remember to use a new name ending in '\_workset'. In this case, we are cloning the workset ‘api\_2\_workset’ shown below.

workset list showing workset to be cloned

The body of this call is still the very simple body (user ID, password, and project). ``` { "context": { "user": "mbj_test", "password": "xxxx", "project": { "name": "imp_payments_demo", "version": "1.0" } } } ``` When run, the response shows the details of the cloned workset.

TDO now shows the cloned workset in the workset listing, and when you edit that workset the details are the same as the one that was cloned.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/api-guide/workset-apis/clone-workset.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.