> For the complete documentation index, see [llms.txt](https://docs.lime-pay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lime-pay.com/api-documentation/support-tickets-api.md).

# Support Tickets API

The Support Ticket API allows you to create and manage support tickets directly from the Merchant Panel. You can flag deposits for review, attach supporting documents, and track your requests — all through simple API calls.

### How it works

Ticket creation follows a **three-step flow**:

1. **Create a draft ticket** — call the create endpoint with the ticket type and description. You will receive a ticket ID.
2. **Attach documents (if needed)** — upload any required files such as vouchers, bank statements, or ID documents. Some documents may be auto-attached for you.
3. **Confirm the ticket** — once everything is ready, confirm the ticket. It gets submitted to our support team and cannot be modified after that.

{% hint style="info" %}
For deposit reviews, you can skip step 1 — use the dedicated deposit endpoints and they will create the draft ticket for you automatically.
{% endhint %}

### Environments

| Environment | Base URL                                 |
| ----------- | ---------------------------------------- |
| Staging     | `https://merchants-api-stg.lime-pay.com` |
| Production  | `https://merchants-api.lime-pay.com`     |

{% hint style="success" %}
We recommend testing your integration in the **Staging** environment before going live in Production.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lime-pay.com/api-documentation/support-tickets-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
