> For the complete documentation index, see [llms.txt](https://docs.bloq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloq.com/readme/accounts-overview.md).

# Accounts Overview

The Bloq Accounts service is central to all Bloq services. The Bloq Accounts service is used to manage access and authenticate users. Through the Bloq Accounts service, users can:

* Manage their Bloq account and profile
* Manage their tokens (e.g., access tokens, refresh tokens) and client-keys
* Manage list of events associated with their Bloq account
* Manage their PGP public keys

Bloq Accounts service can be accessed through the Command Line Interface, SDKs, Bloq Console website, or REST APIs. The [Technical Reference](/advanced-documentation/technical-reference.md) provides information on how to access the Accounts service through the REST API.

### API URL

Account-related operations interact with the URL endpoint found at [accounts.bloq.cloud](https://accounts.bloq.cloud/).

In other words, the above actions (managing your Bloq account, tokens, events, etc.) can only take place once your client hits the Bloq Accounts endpoint URL. The REST API provides a nice insight as to what this activity looks like:

```shell
curl -X GET https://accounts.bloq.cloud/users/me \
  -H 'Authorization: Bearer <AUTH_TOKEN>'
```

The user can interact with the Bloq Accounts service through the above command by accessing the `https://accounts.bloq.cloud/` API URL. More specifically, the above command requests the URL to access the `users/me` endpoint, which returns account-related information such as the account display name, email and Client ID. If a token is not sent, the request to GET the information will be denied.

For Bloq Accounts API calls, an `<AUTH_TOKEN>` is required. You can retrieve your `<AUTH_TOKEN>` via the CLI with the following command:

```shell
bcl conf accessToken
```

When logging in to your Bloq account through the REST API, your `<AUTH_TOKEN>` will be automatically returned alongside a successful login. The [Technical Reference](/advanced-documentation/technical-reference/accounts-api.md) provides a lower level and more thorough walk-through for interacting with the Accounts API URL through the REST API.

{% hint style="success" %}
TIP

The URL is used for back-end communication. If you try to access via web browser, you will reach an unintuitive destination!
{% endhint %}

The following section includes steps to generate a `Client Access Token`. The `Client Access Token` is used to communicate with the BloqNodes service. However, only the `<AUTH_TOKEN>` is accepted for Accounts service operations.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bloq.com/readme/accounts-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
