> For the complete documentation index, see [llms.txt](https://invomagic.gitbook.io/ticketsdocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://invomagic.gitbook.io/ticketsdocs/integrations/about.md).

# About

## Overview

A Tickets Integration allows other services to get information on your use of Tickets!

<figure><img src="/files/4WC9ZeqwcaHwikwPJXEL" alt=""><figcaption><p>Tickets Integrations Logo</p></figcaption></figure>

Currently a Integration must be **authorized** to receive information from Tickets.<br>

## Scopes

A Tickets Integration is granted certain scopes due to its needs but heres an overview for each one that exists\
\
For context heres each scope level\
1: This is the lowest level and contains information that isnt sensitive typically only that a event has indeed occurred\
2: These are higher level scopes, they typically contain more sensitive information such as narrowing specifics\
3: These are super sensitive scopes that contain specific info that could be used to profile you extensively \
4: These are Dangerous scopes that can either get extremely sensitive information or changing server data.

<table data-full-width="true"><thead><tr><th>Scope Name</th><th>Scope Level</th><th>Explanation</th></tr></thead><tbody><tr><td>Get updates on every ticket creation</td><td>1</td><td>When a ticket is created the integration will get a request telling them who created the ticket and the server id where it was created</td></tr><tr><td>Get updates on every transcript creation </td><td>1</td><td>When a channel is transcribed with Professional Transcripts the integration is told who created it and which server created it</td></tr><tr><td>Get updates on every Drop Giveaways and their payouts</td><td>1</td><td>When a Drop giveaway is claimed the integration is told what server dropped it and what amount of XP + Unb currency it paid out</td></tr><tr><td>Get updates on when a person has verified</td><td>1</td><td>When a user verifies the integration will be notified on which server it occurred</td></tr><tr><td>Get Specialized data from ticketing (number of messages)</td><td>2</td><td>When a Ticket has been closed tickets will send the integration the server id and the amount of messages in that ticket.</td></tr><tr><td>Get updates on who verifies</td><td>2</td><td>When a user verifies the integration will be notified on which server it occurred <strong>and who was the one who verified</strong></td></tr></tbody></table>

## Finding Integrations

Integrations can be found using the `/intergrations find` command and will display a list of integrations!

<figure><img src="/files/lu1UMUHQQZ2uIL5p9Mxw" alt="" width="563"><figcaption><p>List with first ever integration</p></figcaption></figure>

## Creating an Integration.

You can create an integration by contacting us here <https://invomagic.com/contact> and select the  "Creating a tickets Integration" option and fill out the details

<figure><img src="/files/ac3AfUVPubg8AqGpbIPI" alt="" width="375"><figcaption></figcaption></figure>

Rules include\
1️⃣ You must treat user data with respect

When you receive data from Tickets you must keep that data secure

2️⃣ You must put it somewhere\
Whether it be in your documentation, it must be easy to find how to setup the integrations on both Tickets and our bot, and easy to find it exists at all

3️⃣ Your bot must be compliant with Discord's TOS&#x20;

This one is obvious

4️⃣ Keep Tickets Integrated Well

If you change the key or the URL you must update it with your t!integrationdev command

5️⃣ Respect

You must respect us, our bot, and the users who use it this includes keeping functionality intact well, running a well kept support server, and clear documentation for your bot and the integration's page\
\
Additionally your integration must only request needed perms + you must not have ever been given a valid BL from CyberShield.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://invomagic.gitbook.io/ticketsdocs/integrations/about.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.