> For the complete documentation index, see [llms.txt](https://developers.bead.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bead.xyz/reference-guide/support-and-contacts/integration-support.md).

# Integration Support

#### Self-serve resources

• Consult the **Reference Guide** and **Operational Guides** for schemas, enums, rate-limit details, and edge-case playbooks.\
• Import the latest **OpenAPI JSON** into Postman or Swagger to view request / response shapes.\
• Search the doc-site FAQs for common integration questions.

#### Opening a support ticket

Send an email to [**support@bead.xyz**](mailto:support@bead.xyz) with the subject line formatted like:

```
[ENV] [SEVERITY]  <one-line summary>
```

Example:\
`[Sandbox] [P2] Webhook signature mismatch during HMAC check`

Include in the body:

* Merchant ID, Terminal ID, Tracking ID, or Payment ID
* UTC timestamps of the failing calls
* Full request / response snippets (sanitised) or cURL examples
* Expected vs. actual behaviour and business impact

#### Ticket triage & acknowledgment

| Severity          | First response  | Typical scenario                         |
| ----------------- | --------------- | ---------------------------------------- |
| **P1 – Critical** | 30 min          | API unavailable, all payments failing    |
| **P2 – High**     | 2 h             | Single merchant blocked, webhook backlog |
| **P3 – Normal**   | 1 business day  | Non-blocking bug, doc clarification      |
| **P4 – Low**      | 2 business days | Cosmetic issue, feature request          |

Support responds within the target above, confirms severity, and outlines next steps.

#### Live troubleshooting for P1 / P2

The on-call engineer may request temporary access logs, HAR files, or a brief screen-share to reproduce the issue. Sandbox credentials or test data may also be exchanged to isolate the fault quickly.

#### Resolution and verification

Bead supplies a fix or workaround and asks you to verify in Sandbox (or Production for urgent cases). The ticket is closed once you confirm resolution. A post-incident summary is delivered for all P1 events within 24 hours of closure.

#### Feedback

Reply in the ticket thread with any comments on response quality or documentation gaps. Your feedback feeds directly into continuous improvements on the docs site and changelog.


---

# 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://developers.bead.xyz/reference-guide/support-and-contacts/integration-support.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.