# Quick Start

## Authenticating Requests

Requests to the API are authenticated using a Bearer token header, the token being your API key.

## Request and Response Format

Requests with a body must be formatted using JSON. Responses with content will be in JSON.

## Make your first request

Before we start, lets set our API Key as a variable in our Shell session.

```shell
APIKey={Your API Key}
```

To make your first request, send an authenticated request to the courses endpoint. This will list all of courses available to your organisation.

{% content-ref url="/pages/D8gObVRDZSaE5z6HFd5M" %}
[GET courses](/api-reference/get-courses.md)
{% endcontent-ref %}

See below for an example of how to perform this call using `curl`:

```shell
curl https://training.tapintosafety.com.au/api/v2/courses \
    -H "Authorization: Bearer $APIKey"
```

That was a big list! Let's narrow it down a little.

```shell
curl https://training.tapintosafety.com.au/api/v2/courses \
    -G -d "categoryType=safety-training" -d "name=Safety" \
    -H "Authorization: Bearer $APIKey"
```

Much easier to read. At the time of writing this request returned just one course, however our library is updating all the time, so maybe you got a few more!


---

# Agent Instructions: 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:

```
GET https://docs.tistraining.com/quick-start.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.