Create a New Work Item Version

The create new work item version API method enables you to create a new version for a work item.

Prerequisites

Before making a 'create new work item version' request, you must have an access token to sign the request. You can retrieve an access token using one of the following flows:

Additionally, you must have the following items in the tenancy for which you are creating a new work item version:

A work item

Overview

The 'create new work item version' API method is a command method. The API client invoking this method must have either a command or a root scope.

This method is useful when you want to display a HotDocs interview or assemble documents from within your own application.

Validating the HotDocs Answer Set XML

When sending HotDocs answer set XML in a begin assembly session request, you must first validate the answer set against the HotDocs answer Set schema.

You can track the progress of your work item version from creation to completion using work item version statuses.

Authentication

See Authentication for more information about authenticating requests to the Advance API.

API Documentation

You can view the latest documentation for the Advance API at http://hotdocsadvance.com/api/rest/documentation/index.html

Request

Request URL

PUT https://{tenancymoniker}.hotdocsadvance.com/api/rest/v2.0/WorkItems/{workItemId}/Versions/{versionId}

Headers

Key	Required	Description	Example value
Authorization	Yes	The Authorization header for the request. Uses the access token retrieved (see Prerequisites section above for more information).	Bearer [access token]

Parameters

Name	Type	Location	Required	Description
tenancymoniker	String	URL	Yes	The tenancy moniker for the tenancy in which you want to create the new work item.
workItemId	Guid	URL	Yes	The Guid for an existing work item.
versionId	Guid	URL	Yes	A new Guid, used to identify the assembly session in Advance.
templatePackageId	Guid	Body	Yes	The ID of a single template package associated with a work item.

Examples

Example Request URL

https://tenancy1.hotdocsadvance.com/api/rest/v2.0/WorkItems/2d9f3d10-6fdb-494f-9929-955515c6f114/Versions/54210021-e86e-429d-ab1b-cc8e101cf7e1

Example Request JSON

{"templatePackageId"; "3d9f3d10-6fdb-494f-9929-955515c6f1945"}

Example Response

Status: 201 OK

Body:

{

"versionId": "32b701fa-fh73-4d58-a70c-71e27c277df9",

"coreAssemblySessionId": "mntekqe11s9w3rhe7u3rfdxws3ur1fhdpo68j74rpw6ofmkcoyn9ene3dzz84bnrh7qcy35geon855o7drgsahi3t9ba8yhg",

"urls": {

"interviewJsUrl": "https://core.hotdocsadvance.com/scripts/interview.js",

"serviceMetadataUrl": "https://core.hotdocsadvance.com/AssemblyService/ipi/session/mntekqe11s9w3rhe7u3rfdxws3ur1fhdpo68j74rpw6ofmkcoyn9ene3dzz84bnrh7qcy35geon855o7drgsahi3t9ba8yhg"

"workItemUrl": "",

}

Using the Response Data

The begin assembly session method provides the following data in its response:

Name	Type	Description	Example data
versionId	Guid	Identifies the assembly session within Advance. You will need this ID when using other API methods that interact with the assembly session. For example, the save, delete, and complete assembly session endpoints.	32b701fa-fh73-4d58-a70c-71e27c277df9
coreAssemblySessionId	Guid	Identifies the assembly session within the Core Assembly Service. You will need this ID when using HD$.AttachSession to display the interview in a user's browser.	mntekqe11s9w3rhe7u3rfdxws3ur1fhdpo68j74rpw6ofmkcoyn9ene3dzz84bnrh7qcy35geon855o7drgsahi3t9ba8yhg
urls.interviewJsUrl	String	The URL from which to load the interview.js file. You must include this in the page on which the interview is displayed.	https://core.hotdocsadvance.com/scripts/interview.js
urls.serviceMetadataUrl	String	The URL for the current assembly session in the Core Assembly Service.	https://core.hotdocsadvance.com/AssemblyService/ipi/session/mntekqe11s9w3rhe7u3rfdxws3ur1fhdpo68j74rpw6ofmkcoyn9ene3dzz84bnrh7qcy35geon855o7drgsahi3t9ba8yhg
urls.workItemUrl	String	The URL for the work item.

You will require this data when displaying an interview.