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

# Auth Overview

> PingBack uses JWT Bearer tokens for authentication.

## Overview

PingBack's API uses JWT (JSON Web Token) Bearer tokens to authenticate requests. You must include a valid token in the `Authorization` header of every request except for `/auth/register` and `/auth/login`.

## Base URL

```
https://api.pingback.live
```

## How to get a token

1. **Register** a new account using [POST /api/v1/auth/register](/api-reference/auth/register).
2. **Log in** with your credentials using [POST /api/v1/auth/login](/api-reference/auth/login). The response includes your `access_token`.

## How to pass a token

Include the token in the `Authorization` header of every authenticated request:

```
Authorization: Bearer YOUR_ACCESS_TOKEN
```

## Token lifetime

Tokens are long-lived. Store them securely and rotate them if you suspect a compromise.

## Endpoints

| Endpoint                                                   | Description                                                    |
| ---------------------------------------------------------- | -------------------------------------------------------------- |
| [POST /api/v1/auth/register](/api-reference/auth/register) | Create a new PingBack user account                             |
| [POST /api/v1/auth/login](/api-reference/auth/login)       | Authenticate and receive a Bearer token                        |
| [GET /api/v1/auth/me](/api-reference/auth/me)              | Retrieve the authenticated user's profile and business context |

<Note>
  All API endpoints except `/api/v1/auth/register` and `/api/v1/auth/login` require a valid Bearer token in the `Authorization` header.
</Note>