> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/integrations/game-development/xbox.md).

# Xbox

Integrate BugSplat for crash reporting in Xbox games (Series X, S, One). Our SDK supports GDK and GDKX projects, helping certified developers enhance game stability.

Using BugSplat enables developers to automatically track crashes in Xbox games, including Xbox Series X, Xbox Series S, and Xbox One, during both development and production phases. Our crash reporting tool supports projects developed with both GDK and GDKX frameworks.

### Accessing the SDK

To request access to the BugSplat SDK, navigate to the [Microsoft Games middleware request page](https://developer.microsoft.com/en-us/games/support/request-gdkx-middleware), select **BugSplat** from the Middleware Partner dropdown, and submit your request. Once Microsoft processes your request and access is granted, BugSplat will deliver the SDK download package and instruction set via the Gaming Consoles tab on the [Database Integrations](https://app.bugsplat.com/v2/database/integrations) page.

For verification of your Xbox Partner status or to learn more about BugSplat's support for Xbox, please contact us at <support@bugsplat.com>.


---

# 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.bugsplat.com/integrations/game-development/xbox.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.
