> 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/nintendo.md).

# Nintendo Switch 2

BugSplat enables developers to automatically track crashes in Nintendo Switch 2 games during development and production.

Access to BugSplat’s Nintendo Switch 2 support is available exclusively to certified Nintendo developers. To get started, follow these steps:

1. **Verify Your Developer Status**\
   Log in to your Nintendo Developer account at <https://developer.nintendo.com/>, and navigate to the **Switch > Middleware** section.\
   Locate **BugSplat** and complete the required authorization process. This step ensures that BugSplat can verify your certification as a Nintendo developer.
2. **Access Tools and Documentation**\
   Once your status is confirmed by Nintendo, you can download the SDK and find comprehensive instructions by navigating to the Gaming Consoles tab on the [Database Integrations](https://app.bugsplat.com/v2/database/integrations) page, under the Nintendo (CRPORTAL) section. From there, you can also manage which Nintendo applications sync with BugSplat; crashes are synced automatically on an hourly basis.

If you have questions or need assistance, reach out to **<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/nintendo.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.