Ellipse Gradient for Header

Thomson Reuters HighQ Integration Guide

Integrate HighQ workspaces, documents, users, tasks, and collaboration content with enterprise systems through authenticated REST APIs and controlled synchronization workflows.

Thomson Reuters HighQ integration options at a glance

Thomson Reuters HighQ’s primary integration mechanism is its authenticated REST API, which provides access to resources such as Sites, Users, Files, Folders, Tasks, and Discussions subject to tenant configuration and permissions. HighQ also exposes file-oriented API resources, although upload, download, versioning, and size limits should be confirmed for the target environment. General webhook coverage, bulk APIs, GraphQL, SOAP, and direct database access were not confirmed. Martini can consume HighQ REST endpoints, store API keys as environment secrets, run scheduled incremental synchronization, map and transform payloads, expose controlled APIs, and handle retries and operational exceptions.

Integration pointSupported by Thomson Reuters HighQ?Common use casesHow Martini supports it
REST APIsYesHighQ’s principal integration mechanism for reading Sites, Users, Files, Folders, Tasks, Discussions, and other resources, subject to API version, tenant configuration, and permissions.Martini can consume authenticated HighQ REST endpoints from workflows, transform payloads, validate responses, and expose controlled orchestration APIs.
File / attachment APIsYesHighQ API resources support file-oriented operations such as retrieving file metadata and, where available, uploading or downloading content associated with Sites and Folders.Martini can orchestrate metadata and binary transfers, preserve file context, map versions, and route size or permission failures for review.
AuthenticationLimitedAPI-key-based access is documented. The effective access of an API key is constrained by HighQ site membership, user permissions, and enabled API capabilities; OAuth 2.0 and JWT were not confirmed as general mechanisms.Martini can store the HighQ API key and endpoint configuration as environment-managed secrets and apply them to outbound REST requests.
Webhooks / outbound callbacksNot confirmedGeneral webhook coverage for changes to Sites, Files, Tasks, Users, or Discussions was not confirmed. Callback support must be verified for each target module and deployment.If a HighQ callback is verified, Martini can expose an API endpoint or webhook-triggered workflow; otherwise, scheduled polling is the safer integration pattern.
Bulk / async / batch APIsNot confirmedA general-purpose HighQ bulk or asynchronous API was not confirmed. Larger transfers should be designed around pagination, controlled extraction, or verified file-based export capabilities.Martini can process pages in bounded workflows, maintain checkpoints, and coordinate controlled batches without assuming a native HighQ bulk endpoint.
Scheduled synchronizationLimitedScheduled polling is an appropriate fallback when required HighQ event notifications are unavailable, using a documented timestamp, cursor, revision, or reconciliation strategy where possible.Martini can schedule workflows, maintain durable cross-references and checkpoints, retrieve changed resources, and retry transient failures.

How Thomson Reuters HighQ exposes data and business events

HighQ REST APIs

HighQ’s documented primary integration mechanism is its authenticated REST API. Available resources and operations depend on the HighQ version, tenant configuration, enabled capabilities, and permissions of the API key.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates with an environment-managed API key, calls the required HighQ resource, handles pagination and response validation, maps the result into a canonical model, and writes it to the target system or exposes it through a controlled Martini API.

Implementation sequence

Authenticate the request with the configured HighQ API key
Call the required HighQ REST resource
Process pagination or incremental markers
Validate the response and required fields
Map the HighQ object to the target model
Apply business rules and write the result

HighQ File APIs

HighQ provides file-oriented API resources for content stored in Sites and Folders. The target API version and tenant should be checked for upload, download, metadata, versioning, and file-size behavior.

Martini implementation pattern

Martini implementation pattern: a workflow retrieves file metadata first, determines whether binary transfer is required, downloads or uploads content through the applicable API operation, preserves identifiers and version information, and sends failures to controlled retry or review handling.

Implementation sequence

Retrieve the HighQ File and its Site or Folder context
Determine whether metadata or binary content is required
Transfer the file using the verified HighQ operation
Preserve the HighQ identifier and version metadata
Map content and metadata to the target repository
Record the transfer result and handle partial failures

HighQ Callbacks

General HighQ webhook and outbound callback coverage was not confirmed. If the target deployment provides callbacks for a specific module, the event contract and delivery behavior must be verified before implementation.

Martini implementation pattern

Martini implementation pattern: Martini exposes a secured API endpoint for the verified callback, validates the incoming request, retrieves the current HighQ resource when necessary, and uses the event as a trigger rather than assuming that every object change is delivered.

Implementation sequence

Verify callback support for the required HighQ module
Receive the callback through a secured Martini API
Validate the event and identify the affected resource
Retrieve the current HighQ object when required
Apply mapping and business rules
Acknowledge or route failures according to the verified delivery contract

Scheduled HighQ Synchronization

Scheduled polling is the fallback when a required HighQ event or callback is unavailable. The workflow should use a documented modification marker, cursor, revision, or durable reconciliation strategy where possible.

Martini implementation pattern

Martini implementation pattern: a scheduler starts a workflow that reads HighQ resources in bounded pages, compares stable identifiers and change markers, processes only new or changed objects, and stores checkpoints or cross-references for the next run.

Implementation sequence

Start the workflow on a controlled schedule
Load the last checkpoint or reconciliation state
Retrieve HighQ resources page by page
Filter new or changed objects
Map and write the changes to the target system
Store the checkpoint and report exceptions

Common Thomson Reuters HighQ integration patterns

Pattern 1: Synchronize HighQ Files to an enterprise repository

When to use this pattern

Use this pattern when matter or project documents stored in HighQ must be indexed, consolidated, or retained in another document platform. Unless tenant-specific event notifications are verified, a scheduled incremental process is the safer trigger.

Integration direction
Thomson Reuters HighQ
Martini
Microsoft SharePoint
Example Mapping
Thomson Reuters HighQ FieldCanonical FieldTarget Field
siteIdworkspaceIdsiteReference
fileIddocumentIdexternalDocumentId
modifiedDatelastModifiedAtmodifiedTime
fileNamedocumentNamename
Martini implementation pattern

A scheduled Martini workflow retrieves Files and metadata from selected Sites or Folders, processes paginated responses, downloads binary content only when needed, and maps metadata to the repository model. It retains HighQ identifiers and modification values for idempotency, applies retention and content rules, and routes permission, size, and transfer failures for retry or review.

Martini capabilities used
  • workflows
  • scheduling
  • API consumption
  • data mapping
  • file handling
  • business rules
  • error handling

Pattern 2: Provision HighQ Sites from Salesforce matters

When to use this pattern

Use this pattern when a Salesforce matter, account, or opportunity reaching a defined stage should create or initialize a HighQ workspace with predictable folders, tasks, or users.

Integration direction
Salesforce
Martini
Thomson Reuters HighQ
Example Mapping
Thomson Reuters HighQ FieldCanonical FieldTarget Field
Salesforce.IdsourceMatterIdexternalReference
Salesforce.NameworkspaceNamesiteName
Salesforce.OwnerIdworkspaceOwneruserReference
Salesforce.StageNameprovisioningStatussiteStatus
Martini implementation pattern

Martini receives or retrieves the Salesforce business event, validates that the matter qualifies for provisioning, checks its cross-reference store, and creates or updates the required HighQ Site through the REST API. The workflow can then create verified Folders or Tasks, record each HighQ identifier, and retry only safe transient operations.

Martini capabilities used
  • API consumption
  • workflows
  • data mapping
  • validation
  • business rules
  • idempotency
  • error handling

Pattern 3: Synchronize HighQ Tasks with Jira

When to use this pattern

Use this pattern when HighQ Tasks need to be coordinated with delivery work in Jira. Define ownership for status, due dates, and assignment before enabling bidirectional updates.

Integration direction
Thomson Reuters HighQ
Martini
Jira
Example Mapping
Thomson Reuters HighQ FieldCanonical FieldTarget Field
taskIdworkItemIdexternalHighQId
titlesummarysummary
statusworkStatusstatus
dueDatedueAtdueDate
Martini implementation pattern

A scheduled Martini workflow retrieves HighQ Tasks, maps assignment and status values, enriches them with source references, and creates or updates Jira issues. A complementary workflow can send approved Jira changes back to HighQ where write operations are available. Source identifiers, ownership rules, and change markers prevent duplicate work and update loops.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • data mapping
  • transformation
  • business rules
  • idempotency
  • retry handling

Pattern 4: Reconcile HighQ Users with Workday

When to use this pattern

Use this pattern for joiner, mover, and leaver workflows or periodic access reviews when the HighQ tenant exposes the required user and membership operations.

Integration direction
Workday
Martini
Thomson Reuters HighQ
Example Mapping
Thomson Reuters HighQ FieldCanonical FieldTarget Field
Workday.Worker_IDpersonIduserReference
Workday.EmailemailAddressemail
Workday.Employment_StatusemploymentStatusaccountStatus
Workday.OrganizationorganizationworkspaceAssignment
Martini implementation pattern

Martini retrieves an approved Workday population and HighQ Users or membership data, compares stable identifiers, and applies only the operations supported by the tenant. Validation, least-privilege access, exception queues, and reconciliation reports ensure that unavailable membership functions do not silently alter access.

Martini capabilities used
  • scheduling
  • API consumption
  • data mapping
  • validation
  • business rules
  • security
  • exception handling

Applications commonly integrated with Thomson Reuters HighQ

HighQ can be connected to adjacent enterprise applications through its REST API, with exact resource coverage and permissions verified for each tenant. The following patterns are common or plausible enterprise architecture scenarios rather than claims of native HighQ integrations.

Application Scenario Direction Martini Pattern
Microsoft SharePoint Synchronize HighQ Files, Folders, and workspace metadata with an enterprise content repository or document collaboration environment. Thomson Reuters HighQ → Martini → Microsoft SharePoint A scheduled Martini workflow retrieves changed HighQ Files and metadata, preserves Site and Folder context, transforms fields to the SharePoint model, and records stable identifiers to prevent duplicate transfers.
Microsoft 365 Coordinate HighQ collaboration metadata, files, or user-related information with Microsoft 365 workloads where both systems expose the required APIs. Thomson Reuters HighQ → Martini → Microsoft 365 Martini orchestrates authenticated API calls in both directions, applies field and permission rules, and routes unsupported or unauthorized objects for review.
Salesforce Create or update HighQ Sites when Salesforce matters, accounts, or opportunities reach a defined stage and return workspace status to Salesforce. Salesforce → Martini → Thomson Reuters HighQ A Martini workflow receives or polls Salesforce changes, validates the business trigger, performs an idempotent HighQ Site operation, and stores a cross-reference between the Salesforce and HighQ identifiers.
iManage Coordinate matter-related documents and metadata between HighQ collaboration areas and an enterprise legal document-management platform. Thomson Reuters HighQ → Martini → iManage Martini retrieves HighQ file metadata or binary content where permitted, maps matter and version fields, transfers the result through the target API, and handles duplicate filenames and version conflicts explicitly.
NetDocuments Synchronize legal matter documents or workspace metadata with cloud legal document management when the required APIs and retention rules are available. Thomson Reuters HighQ → Martini → NetDocuments A scheduled workflow compares stable identifiers and modification markers, transfers only required changes, preserves document context, and records transfer outcomes for reconciliation.
ServiceNow Open or update service requests, governance records, or tasks based on HighQ workspace activity and synchronize operational status back to HighQ where supported. Thomson Reuters HighQ → Martini → ServiceNow Martini polls or receives verified HighQ notifications, maps Tasks or workspace events to ServiceNow records, applies ownership and status rules, and uses retry-safe updates.
Jira Synchronize HighQ Tasks or project milestones with delivery and implementation work items. Thomson Reuters HighQ → Martini → Jira Martini performs scheduled extraction, maps HighQ assignment, status, and due-date values to Jira fields, controls update ownership, and prevents synchronization loops with source identifiers.
Workday Support joiner, mover, and leaver processes or workspace access reconciliation involving HighQ Users and site membership. Workday → Martini → Thomson Reuters HighQ A scheduled Martini workflow compares approved Workday populations with HighQ Users or membership data, applies access rules where tenant APIs permit, and reports exceptions without exposing sensitive credentials.

How to build a Thomson Reuters HighQ integration in Martini

Objective

Establish the HighQ endpoint and API-key authentication without embedding credentials in workflow definitions or source-controlled configuration.

Instructions in Martini

  • Confirm the HighQ API version, tenant endpoint, required header or parameter format, and permissions.
  • Store the API key and endpoint configuration as Martini environment-managed secrets.
  • Test access with a least-privilege account representative of production permissions.

Objective

Select an event, callback, API, or scheduled trigger based on what the target HighQ deployment actually supports.

Instructions in Martini

  • Use a verified HighQ callback only when its module coverage and delivery contract are documented.
  • Use a Martini Scheduler Trigger for resources without confirmed event support.
  • Define an incremental marker, cursor, or reconciliation strategy before enabling polling.

Objective

Read HighQ resources efficiently and reliably, including paginated Sites, Users, Files, Folders, Tasks, or Discussions.

Instructions in Martini

  • Call the documented HighQ REST resource from the workflow.
  • Process pages or bounded batches instead of assuming the first response is complete.
  • Retrieve binary File content only when required by the target process.

Objective

Coordinate calls, cross-references, transformations, and target writes as a maintainable Martini workflow.

Instructions in Martini

  • Separate retrieval, validation, mapping, business rules, and target operations into clear workflow stages.
  • Persist HighQ identifiers, source identifiers, and checkpoints needed for replay and reconciliation.
  • Use reusable services or workflow components for common API and error-handling behavior.

Objective

Convert HighQ resource structures into the canonical and target data models while preserving important context.

Instructions in Martini

  • Map Site, Folder, File, Task, User, and Discussion identifiers explicitly.
  • Preserve Site and Folder context, file versions, timestamps, and source references where relevant.
  • Normalize status, assignment, date, and content-type values before writing to the target.

Objective

Apply authorization, ownership, deduplication, retention, and eligibility rules before changing either system.

Instructions in Martini

  • Check whether the object is within the permitted Site, Folder, and user scope.
  • Use stable identifiers and cross-reference checks before creating Sites, Tasks, Folders, or Files.
  • Define field ownership for bidirectional synchronization to prevent update loops.

Common Thomson Reuters HighQ data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
SitesHighQ workspaces for matters, projects, teams, and collaboration areas.Salesforce, Microsoft SharePoint, ServiceNow, iManage, NetDocumentsMartini maps Site identifiers and metadata, applies idempotent create-or-update rules, and stores cross-references to source applications.
UsersHighQ user profiles and user-related access or membership information.Workday, Microsoft 365, identity administration systemsMartini reconciles approved user populations, validates permissions, minimizes sensitive fields, and reports unavailable administrative operations.
FilesDocuments and other content stored in HighQ Sites and Folders.Microsoft SharePoint, iManage, NetDocuments, records platformsMartini processes metadata and, where supported, binary content while preserving identifiers, versions, content types, and Site or Folder context.
FoldersOrganizational containers for HighQ Files and workspace content.Microsoft SharePoint, iManage, NetDocuments, records platformsMartini maps folder hierarchy and stable identifiers, validates parent relationships, and handles missing or unauthorized containers as exceptions.
TasksWork items assigned to HighQ users or teams, including status and due-date information.Jira, ServiceNow, Salesforce, project-management platformsMartini maps assignment, status, dates, and references, applies ownership rules, and prevents update loops during bidirectional synchronization.
DiscussionsCollaboration and conversation content associated with HighQ workspaces.Reporting platforms, knowledge repositories, enterprise collaboration systemsMartini retrieves permitted discussion content, applies privacy and retention rules, and transforms content only where the target system supports the required model.

Authentication and security considerations

API-key authentication

HighQ API access is documented around API keys. The exact header or parameter format must be confirmed against the target HighQ API version and tenant.

Permissions and least privilege

An API key can authenticate successfully while still lacking access to a particular Site, Folder, File, User, Task, or Discussion. Validate site membership, object permissions, and enabled API capabilities with a least-privilege production-like account.

Secret protection

  • Store HighQ API keys in Martini environment-managed secrets.
  • Do not embed credentials in workflow definitions or source-controlled configuration.
  • Use HTTPS and restrict logs so that API keys, confidential legal information, and document content are not exposed.

Authentication boundaries

OAuth 2.0, JWT, and general OAuth-style scopes were not confirmed as standard HighQ REST mechanisms. Do not assume they are available without tenant-specific documentation.

Operational considerations for Thomson Reuters HighQ integrations

Rate limits and pagination

Confirm HighQ request limits, concurrency restrictions, and API-key quotas. Treat collection responses as paginated unless the endpoint documentation states otherwise, and use bounded concurrency with backoff.

Incremental synchronization

Prefer a documented modification timestamp, cursor, revision, or equivalent filter. If no reliable change marker exists, use scheduled reconciliation and retain durable cross-references.

Idempotency and retries

Use stable HighQ identifiers rather than names or paths. Before creating Sites, Tasks, Folders, or Files, check for an existing cross-reference. Retry only operations that are safe to repeat.

File transfers

Verify file-size limits, binary versus metadata behavior, versioning, content types, Site and Folder context, duplicate filenames, interrupted transfers, malware scanning, and downstream retention rules.

Schema and permissions

Confirm the HighQ API version and resource availability. Validate required fields explicitly, tolerate additive fields, monitor enumerated values, and distinguish authentication failures from authorization failures.

Testing and monitoring

Test with representative Sites, Files, Users, Tasks, and permissions before production. Capture safe request and response diagnostics, monitor workflow outcomes, and avoid logging API keys or sensitive document content.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration beyond point-to-point calls

Martini coordinates HighQ API calls with validation, business rules, transformations, cross-reference storage, and target-system writes in maintainable workflows.

Reliable synchronization

Instead of a single-purpose script, Martini can combine scheduled execution, pagination, checkpoints, idempotency rules, bounded retries, and exception routing for operationally dependable synchronization.

Controlled API exposure

Martini can expose a controlled API façade for internal applications that need HighQ data, while keeping HighQ credentials, permissions, and implementation details behind the integration boundary.

Reusable integration assets

Common authentication, mapping, validation, file-handling, and error-handling logic can be reused across HighQ workflows and adjacent enterprise integrations without claiming a dedicated native connector.

Frequently asked questions

How can Thomson Reuters HighQ be integrated with enterprise systems?

HighQ is primarily integrated through its authenticated REST API. Enterprise workflows can read and, where supported, create or update Sites, Users, Files, Folders, Tasks, and Discussions. File-oriented operations should be verified for the target API version and tenant. Where event notifications are unavailable, scheduled incremental synchronization can be used.

Can Martini integrate with Thomson Reuters HighQ?

Yes. Martini can consume the HighQ REST API, store API keys as environment-managed secrets, orchestrate workflows, map HighQ objects to other systems, expose controlled APIs, and run scheduled synchronization. Any HighQ callback support should be verified for the relevant tenant and module.

Do I need a connector to integrate Thomson Reuters HighQ with Martini?

No. A dedicated HighQ connector is not required. Martini can integrate using HighQ’s confirmed REST API and API-key authentication, together with verified file operations or callbacks and scheduled workflows where appropriate.

Is there any extra Lonti cost to integrate Thomson Reuters HighQ with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate HighQ. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from Thomson Reuters HighQ, infrastructure providers, or other third-party systems depending on subscriptions, usage, and deployment model.

Which HighQ integration methods should new projects use?

Use the HighQ REST API as the primary method, with API-key authentication and permissions verified for the target tenant. Use file-oriented API resources for document transfers where supported. GraphQL, SOAP, general bulk APIs, and direct database access were not confirmed and should not be assumed.

Can HighQ send events or webhooks for changes?

General webhook coverage for HighQ changes was not confirmed. Callback or event support must be checked for each required module and deployment. If the required notification is unavailable, Martini can use scheduled polling with pagination and a documented change marker or reconciliation process.

How does Martini synchronize and transform HighQ data?

Martini workflows retrieve HighQ resources, process pagination, map fields into canonical and target models, apply business rules, and write results to downstream applications. Stable HighQ identifiers, source references, modification markers, and checkpoints support incremental synchronization and duplicate prevention.

How are HighQ errors, retries, and duplicate operations handled?

Martini can classify authentication, authorization, validation, rate-limit, not-found, and transient server failures, retry only safe transient operations with backoff, and route persistent failures for review. Idempotency is implemented with stable HighQ identifiers, cross-reference records, and create-or-update checks.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Connect Thomson Reuters HighQ with Martini

Use Martini to build secure HighQ integrations around REST APIs, file operations, scheduled synchronization, data mapping, and controlled enterprise workflows.

EXPLORE MARTINI
BOOK A DEMO