apidocs

GetAppliedTags API

Returns all tags applied to a document. Each tag entry includes the tag text, the date it was applied, the user who applied it, the document version it belongs to, and workflow context when the tag was applied via a workflow step.

Endpoint

/srv.asmx/GetAppliedTags

Methods

Parameters

Parameter Type Required Description
authenticationTicket string Yes Authentication ticket obtained from AuthenticateUser.
path string Yes Full infoRouter path to the document (e.g. /MyLibrary/Reports/Report.pdf).

Response

Success Response

Returns a <response> element with success="true" containing an <AppliedTags> element with zero or more <AppliedTag> child elements. Results are ordered by TagDate ascending.

<response success="true" error="">
  <AppliedTags>
    <AppliedTag
      TagText="Approved"
      TagDate="2024-01-15T10:30:00Z"
      VersionNumber="2"
      VersionNumberMultiPart="2.0"
      TaggedById="42"
      TaggedByName="John Doe"
      WorkFlowId="7"
      WorkFlowName="Document Approval"
      WorkFlowStepNumber="3" />
    <AppliedTag
      TagText="Final"
      TagDate="2024-02-01T09:00:00Z"
      VersionNumber="3"
      VersionNumberMultiPart="3.0"
      TaggedById="15"
      TaggedByName="Jane Smith"
      WorkFlowId="0"
      WorkFlowName=""
      WorkFlowStepNumber="0" />
  </AppliedTags>
</response>

No Tags Applied Response

When no tags have been applied to the document:

<response success="true" error="">
  <AppliedTags />
</response>

Error Response

<response success="false" error="[900] Authentication failed." />

Response Attributes

Each <AppliedTag> element carries the following attributes:

Attribute Type Description
TagText string The tag label text, exactly as defined in the tag definitions.
TagDate datetime UTC date and time when the tag was applied.
VersionNumber integer The version number of the document to which the tag was applied.
VersionNumberMultiPart string Human-readable version number (e.g. 2.0).
TaggedById integer User ID of the user who applied the tag.
TaggedByName string Full name of the user who applied the tag.
WorkFlowId integer ID of the workflow that applied the tag, or 0 if applied manually.
WorkFlowName string Name of the workflow that applied the tag, or empty string if applied manually.
WorkFlowStepNumber integer Step number within the workflow that applied the tag, or 0 if applied manually.

Required Permissions

The caller must be authenticated and must have view (read) access to the document. If the document does not exist or the caller lacks access, the API returns success="false".


Example

GET Request

GET /srv.asmx/GetAppliedTags
  ?authenticationTicket=3f2504e0-4f89-11d3-9a0c-0305e82c3301
  &path=/TestDomain/TestFolder/report.pdf
HTTP/1.1

POST Request

POST /srv.asmx/GetAppliedTags HTTP/1.1
Content-Type: application/x-www-form-urlencoded

authenticationTicket=3f2504e0-4f89-11d3-9a0c-0305e82c3301&path=/TestDomain/TestFolder/report.pdf

SOAP Request

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
               xmlns:tns="http://tempuri.org/">
  <soap:Body>
    <tns:GetAppliedTags>
      <tns:authenticationTicket>3f2504e0-4f89-11d3-9a0c-0305e82c3301</tns:authenticationTicket>
      <tns:path>/TestDomain/TestFolder/report.pdf</tns:path>
    </tns:GetAppliedTags>
  </soap:Body>
</soap:Envelope>

Notes



Error Codes

Error Description
[900] Authentication failed Invalid or missing authentication ticket.
[901] Session expired or Invalid ticket The ticket has expired or does not exist.
Document not found error The path does not resolve to a document, or the caller lacks view access.