> This page is for Unified.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.merge.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.merge.dev/_mcp/server.

# Analyze security controls

> How to analyze ticket assignments and status to assess security control posture using the Merge Ticketing API.

---

#### User authorizes ticketing access

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

#### Retrieve ticket data

Your compliance app is able to get the data it needs with:
[**GET** /Tickets](https://docs.merge.dev/ticketing/tickets/#tickets_list) to retrieve the end-user's tickets, with access to key fields: `status`, `description`, `collections`, `ticket type`, `attachments`, `due date`.

#### Sync ticket updates

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`)

#### Surface compliance insights

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.

#### Automate security processes with Merge

Integrate today or talk to our sales team to learn how Merge unlocks hundreds of integrations in days - not years.

\


Get a demo **

\
\