---
title: "What your API key resolves to"
method: GET
path: "/v1/whoami"
---

# What your API key resolves to

`GET /v1/whoami`

## Request

- Base URL: `https://api.reqbeat.com`
- URL: `https://api.reqbeat.com/v1/whoami`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

What the presented key resolves to. The response can only ever reflect
the presented key's own customer, never another's.

## Response `200`

Successful Response

- WhoamiResponse
  - `customer_id` string, required
  - `account_id` integer, required
  - `tier` string, required: The id of the tier this key runs on, e.g. 'tier_1' -- the value `/v1/pricing` lists as `quota_tier`.
  - `tier_name` string, required: The public name of that tier, e.g. 'Trial' -- the name `/v1/pricing` lists it under. It names the limits the key runs on, not what the account is billed.
  - `scopes` string[], required

## Other responses

- `401`: No API key was sent.
- `403`: A key was sent, but it is unknown or revoked.

---

[API](https://skmtc.dev/reqbeat/apis/reqbeat-api.md) · [All operations](https://skmtc.dev/reqbeat/apis/reqbeat-api/llms.txt) · [OpenAPI document](https://skmtc.dev/reqbeat/apis/reqbeat-api/revisions/4758e5957e8c?raw)