Track compliance
Use ticketing data to track org level compliance with security standards such as SOC2
Your user authorizes your application to access their ticketing platform via an OAuth or similar authorization flow through Merge Link.
Use GET /Collections, GET /Tickets, and GET /Users to ingest collections, tickets, and users from your users’ account.
Leverage Merge webhooks to ensure you’re pulling real-time data.
Using the data collected in the previous step, confirm the presence of required ticketing infrastructure like a triage system.
If you’re only looking to update tickets created after a certain time period or part of a specific project you can use various query parameters to GET this including created_after or collection_id.
Keep evidence up to date and track changes. You can build a frontend so your users’ can track their compliance overtime.
Set up third-party webhooks, if supported, to set up real-time alerts like if there’s a change to end user data.
Leverage Merge’s POST /Tickets to create tickets related to compliance in your customer’s ticketing platform.