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

# GET /v1/me — Verify Your Knock2 API Key

> GET /v1/me confirms your API key is valid and returns the tenant (product_slug) it belongs to. Use this as a connection test in integrations.

Use `GET /v1/me` as a health check or connection-test step — it confirms the API key is valid and returns the tenant it belongs to. This endpoint is ideal for validating a newly issued key or testing connectivity during integration setup. It intentionally returns the minimum possible payload and does not include the key's scopes.

## Endpoint

```text theme={null}
GET https://api.knock2.ai/v1/me
```

This endpoint requires only the `Authorization` header. It accepts no path parameters, query parameters, or request body.

## Example Request

```bash theme={null}
curl https://api.knock2.ai/v1/me \
  -H "Authorization: Bearer YOUR_API_KEY"
```

## Response

A successful request returns `200 OK` with a `MeResponse` body.

```json theme={null}
{
  "data": {
    "product_slug": "your_tenant",
    "status": "ok"
  }
}
```

<ResponseField name="data.product_slug" type="string">
  The unique tenant identifier this API key belongs to. Use this value to confirm you are authenticating against the correct Knock2 tenant.
</ResponseField>

<ResponseField name="data.status" type="string">
  Always `"ok"` for a successful response.
</ResponseField>

## Error Responses

| Status | Meaning                                                              |
| ------ | -------------------------------------------------------------------- |
| `401`  | The API key is missing, malformed, or has been revoked.              |
| `422`  | Request could not be processed — verify your request is well-formed. |
| `429`  | Rate limit exceeded. Slow down your request rate and retry.          |