> ## Documentation Index
> Fetch the complete documentation index at: https://developers.scoutworks.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Postman, Bruno and Insomnia

> Load every endpoint into your API client in one step.

Every API client can read our OpenAPI file. It describes every endpoint, parameter and response, and it needs no key:

```text theme={null}
https://api.scoutworks.app/api/v1/openapi.json
```

## Postman

Open our public Postman workspace, then fork the **Scoutworks API** collection. It comes with a **Demo sandbox** environment that already holds the sandbox key, so the first request works straight away.

<Card title="Scoutworks API in Postman" icon="rocket" href="https://www.postman.com/david-596ca7ed-6044918/scoutworks">
  Fork the collection and the Demo sandbox environment.
</Card>

To use your own group, fork the environment, change `baseUrl` to `https://api.scoutworks.app/api/v1` and set `apiKey` to your key. Store the key as a **secret** variable, so Postman hides it.

You can also import the file yourself: **Import → Link**, then paste the OpenAPI address.

## Bruno

<Steps>
  <Step title="Import the file">
    Choose **Import Collection → OpenAPI V3 Spec**, and paste the OpenAPI address.
  </Step>

  <Step title="Add the key">
    Open the collection settings. Under **Auth**, choose **Bearer Token** and paste the [sandbox key](/guides/sandbox) or your own.
  </Step>
</Steps>

Bruno keeps collections as files in a folder. Do not commit a real key to git: put it in a Bruno environment marked **secret**.

## Insomnia

Choose **Import → From URL**, and paste the OpenAPI address. Then set a **Bearer Token** on the collection.

## Other tools

Most tools that speak OpenAPI can use the same file. For example, you can generate a typed client with [OpenAPI Generator](https://openapi-generator.tech) or [openapi-typescript](https://openapi-ts.dev). The file is updated with every change to the API. See the [changelog](/changelog).
