<!-- https://missblue.dev/docs/identity -->

# Identity

One call, and the first one to make. The webhook routes take a project id in the path, and nothing else returns one — so without this a key could act on its project without being able to name it.

Base URL: `https://api.missblue.dev`

Every request carries `Authorization: Bearer $MISS_BLUE_KEY`.

### GET /v1/me

What this credential is.

For a key: its id, its project, and the organization above it. `live` is false for a sandbox or legacy test key. `sandbox: true` identifies an isolated mb_sandbox_ key; legacy mb_test_ keys still access real traffic. There is no person in the answer, because there is no person behind a key.

Example:

```bash
curl -X GET https://api.missblue.dev/v1/me \
  -H "Authorization: Bearer $MISS_BLUE_KEY"
```

Response:

```json
{
  "kind": "key",
  "key_id": "2aea3032-1631-419a-ba45-05cb965d157c",
  "project_id": "e3b7c534-7e5d-4669-b90a-5b617bfe77f0",
  "project_name": "Client Support",
  "workspace_id": "3480fdd8-2ef3-4edd-9949-bf78b4cd3e35",
  "workspace_name": "Acme Agency",
  "live": true
}
```