> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/rest-api-reference/accounts/users.md).

# User Info

Verify the authenticated Blotato user, subscription information, and account usage through REST.

## Users

### General

Use these endpoints to verify your API key and check account usage.

### Endpoints

<mark style="color:blue;">**GET**</mark> `/v2/users/me`

Fetches the current user's information, including subscription status and plan. This endpoint is useful for verifying that your API key is valid and referencing your own `userId`.

#### Response Keys

| Name                 | Type     | Description                                                     |
| -------------------- | -------- | --------------------------------------------------------------- |
| `id`                 | `string` | The unique ID of the user.                                      |
| `subscriptionStatus` | `string` | The user's subscription status (e.g., `active`, `generic_pro`). |
| `subscriptionPlan`   | `string` | The user's plan tier: `starter`, `creator`, or `agency`.        |
| `apiKey`             | `string` | **\[Sensitive]** The user's API key.                            |

***

## Examples

### Get verification info

```http
GET https://backend.blotato.com/v2/users/me HTTP/1.1
blotato-api-key: blt_...
```

**Response 200 OK**

```json
{
  "id": "e931cdad-0c31-4191-8930-745a76c8e31a",
  "subscriptionStatus": "active",
  "subscriptionPlan": "creator",
  "apiKey": "blt_..."
}
```

***

<mark style="color:blue;">**GET**</mark> `/v2/users/me/usage`

Returns the current user's connected-account usage, active-contact usage, and active-contact limit.

Use this endpoint before connecting more accounts or sending messages at scale so you know how close you are to your plan limits. For the limit values on each plan, see [Plan Limits](/settings/billing-and-credits.md#plan-limits).

#### Response Keys

| Name            | Type                       | Description                                                                                                                                                                                    |
| --------------- | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `accounts`      | `integer`                  | Number of connected channels counting toward the connected-accounts limit. Facebook Pages count. The Facebook login itself does not count. LinkedIn profiles and LinkedIn company Pages count. |
| `contacts`      | `integer`                  | Number of contacts messaged this month, counting toward the active-contacts limit.                                                                                                             |
| `contactsLimit` | `integer` or `"unlimited"` | Maximum active contacts you can message this month. This matches your current account limit, including any custom active-contact limit on your account.                                        |

### Get usage

```http
GET https://backend.blotato.com/v2/users/me/usage HTTP/1.1
blotato-api-key: blt_...
```

**Response 200 OK**

```json
{
  "accounts": 12,
  "contacts": 438,
  "contactsLimit": 6000
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.blotato.com/rest-api-reference/accounts/users.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.