Your user authenticates via Merge Link to authorize an integration between their Ticketing third-party platform and Merge. Merge begins syncing data.

Your compliance app is able to get the data it needs with:

• GET /Tickets to retrieve the end-user's tickets, with access to key fields: status, description, collections, ticket type, attachments, due date.

After your initial sync, depending on how frequent you need to pull ticket information for compliance, call the endpoint using the modified_after query parameter to tickets.

• If you only require Tickets completed after a certain date, simply use "completed_after” string (ex. GET /tickets?completed_after=2022-02-02T00:00:00Z)

Depending on how you are surfacing relevant compliance controls to your customers, you will need to write logic to clearly show the relevant information from the tickets.

• For example, the logic can automatically surface compliance control status in your product’s front-end such as a dashboard or a report.