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

# Full Setup Guide

Getting up and running with BugSplat is a well-documented, straightforward process that thousands of developers have followed. There are two ways to start:

* **Just want to see it work?** [Post a sample crash in about 5 minutes](/getting-started/quickly-submitting-your-first-crash-in-under-5-minutes.md), no code required.
* **Ready to integrate your own app?** Follow the six steps below. It takes about as long as it does to drink a [large mug](https://shop.spacex.com/collections/accessories/products/occupy-mars-heat-sensitive-terraforming-mug-new) of coffee.

{% embed url="<https://bugsplat.wistia.com/medias/qp13mure3h>" %}

## ✍️ The BugSplat 6-Step Checklist

1. [Sign up for a BugSplat account](/getting-started/signing-up-for-an-account-with-bugsplat.md)
2. [Create a database](/getting-started/create-a-new-database-in-bugsplat.md)
3. [Add your team and tools](/getting-started/adding-uses-to-your-account.md)
4. [Integrate your platform](/integrations/integrations.md)
5. [Submit your first report](/getting-started/posting-a-test-crash.md)
6. [Learn to use the app](/guides/development.md)

## 🖇️ More Details

Following the above steps takes new users from [creating an account](/getting-started/signing-up-for-an-account-with-bugsplat.md) and [database](/getting-started/create-a-new-database-in-bugsplat.md), through [adding your team and tools](/getting-started/adding-uses-to-your-account.md), to [integrating your application](/integrations/integrations.md) and [posting your first report](/getting-started/posting-a-test-crash.md). Crash reporting is more fun with friends, so bring your team along early. It mirrors the in-app Onboarding Tool.

Once these steps are complete, users should learn more about using the BugSplat app in the [Development](/guides/development.md) section which has a handy [walkthrough of the BugSplat application](/guides/using-the-app.md), 3rd party integration guides, and much more.

If at any point you get stuck and want some help, please reach out to us via our [Discord](https://discord.gg/K4KjjRV5ve) or by sending us an [email](mailto:support@bugsplat.com).

{% hint style="success" %}
🧙‍♂️ **Attention new accounts**: You will also have the opportunity to follow these steps via the Onboarding Tool that's visible to new users right after they [create an account](/getting-started/signing-up-for-an-account-with-bugsplat.md).
{% 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 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://docs.bugsplat.com/getting-started/getting-started.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.