---
title: "Authentication | Skylar"
description: "How to authenticate requests to the Skylar Reporting API using a bearer token, including a quick test call and error handling."
url: "https://www.getskylar.com/docs/guides/authentication"
---

# Authentication

Use a Reporting API key on every request:

```
Authorization: Bearer <api-key>
```

## Get your API key

Open [Reporting Access](https://app.getskylar.com/reporting-access) in the Skylar app.

The `New Secret` shown there is your Reporting API key. Use that value as the bearer token in every request.

## Base URL

Production base URL:

```
https://europe-west2-firebase-frontend-v01.cloudfunctions.net/reportingApi
```

All endpoints in these guides are relative to that base URL.

## Copy-paste quick test

```
REPORTING_API_BASE_URL="https://europe-west2-firebase-frontend-v01.cloudfunctions.net/reportingApi"
SKYLAR_REPORTING_API_KEY="<secret from Reporting Access>"
```

```
curl --request GET \
  --url "$REPORTING_API_BASE_URL/v1/users" \
  --header "Authorization: Bearer $SKYLAR_REPORTING_API_KEY"
```

## Unauthorized response

If the bearer token is missing or malformed, the API returns:

```
{
  "error": {
    "code": "unauthorized",
    "message": "Authorization header must include a Bearer token."
  }
}
```

## Next steps

-   Use [`GET /v1/users`](https://www.getskylar.com/docs/guides/list-users) to fetch the user directory visible to your API key.
-   Keep the full [API reference](https://www.getskylar.com/docs/api-reference) open for schema details.
-   Use the [raw OpenAPI JSON](https://www.getskylar.com/docs/openapi/reporting-api-v1.json) when you need the machine-readable contract.
