# General Overview

## Prerequisites

Before you begin integration:

1. **Contact your Echo Account Team** to obtain your `client_id` and
`client_secret`.
2. Ensure your system can make HTTPS requests using
`application/x-www-form-urlencoded` request bodies and process JSON
responses.
3. Confirm your application can cache and manage Bearer tokens dynamically
across their full lifetime.
4. Review the [Full specification](/authorizer-api/openapi) for complete endpoint
and schema details.


## API Endpoint

| Method | Endpoint | Purpose |
|  --- | --- | --- |
| `POST` | `/token` | Exchange credentials for an OAuth 2.0 Bearer token |


## Token Generation Workflow

When your application calls `POST /token`:

1. **Submission** — Your `client_id`, `client_secret`, `grant_type`, and
`scope` are sent as form data.
2. **Validation** — The EchoSync Authorizer verifies your application identity
and credentials.
3. **Response** — A JSON payload is returned containing the `access_token`,
`expires_in` (seconds), `token_type`, and approved `scope`.