> For the complete documentation index, see [llms.txt](https://docs.keyshade.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keyshade.io/contributing-to-keyshade/running-things-locally/api-testing.md).

# API Testing

⁸---\
description: API testing using Bruno

***

## API Testing

We use Bruno to test our APIs. All of our endpoints are tested using Bruno and we maintain a detailed documentation of every endpoint in our Bruno collection. You can find it in [here](https://github.com/keyshade-xyz/keyshade/blob/develop/api-collection/README.md).

Although we recommend to use Bruno, you can always import the collections into your favorite tool.

### Getting started

* For starters, make sure you have Bruno installed on your system. If not, you can download it from [here](https://www.usebruno.com/downloads)

![Download Bruno](/files/WfoMjVyuV7s4GUzBtKsl)

* Once you have Bruno installed, open it up.

![Open Bruno](/files/Tsb2ZO5XTjDrzGPlazWI)

* Click on `Import Collection`

![Import Collection](/files/gtcSY36UcmDQUhTDMg24)

* Point to the [`api-collection`](https://github.com/keyshade-xyz/keyshade/blob/develop/api-collection/README.md) folder

![API Collection](/files/VSpcB0U815eFJeWWAig5)

* For every collection in the API, the requests hold one or more examples that you can use to test the API. You can also find the schema of the request itself.

### Making changes to the API

Whenever you make a change to the API that adds / removes / updates one or more requests, you are required to update the corresponding collection in the [api-collection](https://github.com/keyshade-xyz/keyshade/blob/develop/api-collection/README.md) folder. Since the collections are tracked in the branch, we expect you to make all the changes in the same branch which you are working on.


---

# 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.keyshade.io/contributing-to-keyshade/running-things-locally/api-testing.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.