HotDocs Advance API Reference Documentation
You can view the latest documentation for the Advance API at http://hotdocsadvance.com/api/rest/documentation/index.html
The reference documentation contains details of all public API methods. For selected examples of using the API, see Using the API Overview.
Answer Set Schemas
Some HotDocs Advance API methods may require you to send a HotDocs Answer Set with the request. The answer set must be validated against the HotDocs Answer Set schema before the request is sent.
API Resources
When making an HTTP request, the following resources are available in the Advance API.
See also: Advance concepts for API users.
Resource | Description | Related Tasks |
Branding | The logo which displays on your Advance site and for client and public interviews. |
|
ClientAccounts | The data of external clients held by Advance for the purposes of client interviews. |
|
ClientInterviews | A client interview is an interview you send via email to an external user to gather their data. |
|
PublicInterviewLinks | A public interview link is a link to an interview which you can place on your website to gather data from an unknown external user, such as a prospect. |
|
Subscriptions | Details of your Advance subscription. |
|
TemplatePackages |
A template package is a zipped package of files sent to Advance when a template is uploaded from HotDocs Author. The template package contains the template files and associated metadata files. |
|
TemplatePackageVersions | When you upload a zipped template package from Author, Advance creates a new version of the template. Before users can assemble a document, a template must have a live version. |
|
UserGroups | A user group is a collection of user accounts, used to control access to work groups. Users can only access a work group if they are included in a user group that is allocated to that work group. |
|
Users | A user account within Advance. Users may have additional administrative roles, which provide them with authorization to perform specific actions in Advance. |
|
WorkGroups | A work group is a named location in which users can create work items. Users can only create work items in a work group if they are included in a user group that is allocated to that work group. Work groups are used to control access to template packages; users can only access template packages which have been allocated to their work group. |
|
WorkItems |
A work item is a named entity in HotDocs Advance with which you can enter and edit answer data, and assemble documents from that data, for a specific template package. Users create work items through their allocated work groups. By default, work items are accessible to any user that has access to the work group. You can make work items private, so that only the user that created the work item can access it. |
|
Additional Terms
This table provides details of some of the additional terms used by the resources and endpoints above.
Resource | Description | Related Tasks |
AnswerFile | An answer file is XML that comprises an answer set. When creating a work item using the API, you can optionally supply an XML string in the request. Advance can then assemble documents for the work item using the supplied answer file. |
|
AssemblySessions
|
An assembly session is a specific instance of the document assembly process in the Core Assembly Service. Using assembly sessions, you can manage the creation of new versions of a work item and assemble documents. In-progress assembly sessions can be saved or completed. | |
DefaultAnswers | The work group default answer set is a basic set of answers used across work items in a work group. |
|
Documents | The assembled documents created by processing an answer file and template package in an assembly session. |
|
Images | Images associated with a work item as part of the answer file. |
|
LiveDate | The date and time from which a template package version is made accessible to users. |
|
PostProcessingComplete | The status of a work item using the Post-assembly Processing Event webhook. |
|
Roles | A set of administrative roles allocated to users to control permissions. |
|
VariableData | The variables used in a template package. |
|
Versions | When a user completes an assembly session, Advance creates a new version of the work item, with a new set of assembled documents. |
|