canonical: https://jentic.com/apis/att.com/att

# AT&T OAuth

The AT&T OAuth API is the token endpoint for the AT&T developer platform. It implements the OAuth 2.0 client-credentials flow at `/oauth/v4/token`, returning the access tokens that other AT&T platform APIs require for authentication. Although the API itself has a single operation, that operation is the gating step for any AT&T platform integration - without it, downstream AT&T services cannot be called.

## For AI agents

Mint OAuth 2.0 access tokens for AT&T platform APIs by calling the AT&T client-credentials token endpoint.

## Scope

Does not handle SMS, voice, billing, or downstream AT&T platform APIs - use for issuing and refreshing OAuth 2.0 access tokens only.

## Capabilities

- Obtain a fresh OAuth 2.0 access token via POST `/oauth/v4/token` using client credentials
- Refresh access tokens before expiry to keep AT&T platform calls authenticated
- Issue per-scope tokens for downstream AT&T APIs that require scoped credentials
- Centralise AT&T platform authentication for an agent that fans out to multiple AT&T services

## Use cases

### Token Issuance for AT&T Platform Integrations

Any service calling AT&T platform APIs needs an OAuth 2.0 access token before it can issue requests. The AT&T OAuth API's POST `/oauth/v4/token` implements client-credentials issuance, returning a bearer token tied to the requested scopes. An agent then uses that token in the Authorization header for downstream AT&T calls. Token issuance and refresh logic stays isolated in this single endpoint.

Example prompt: POST to `/oauth/v4/token` with grant_type=client_credentials, client_id and client_secret, and capture the returned access_token and expires_in

### Scheduled Token Refresh

Long-running AT&T integrations need to refresh tokens before expiry to avoid 401 retries. A scheduler agent calls `/oauth/v4/token` on a cadence shorter than expires_in, caches the latest token, and rotates it into the downstream AT&T API client. This prevents window-edge auth failures during high-volume operations.

Example prompt: Run a scheduled task that requests a new token at expires_in / 2 and updates the cached value used by downstream AT&T API clients

### AT&T Token Management via Jentic

Through Jentic, an AI agent calling an AT&T platform API never handles the OAuth client_id or client_secret directly. Jentic stores both in the encrypted vault, calls `/oauth/v4/token` on demand, and injects the resulting bearer token into downstream AT&T API requests. This collapses AT&T auth into a single Jentic configuration step.

Example prompt: Use Jentic to search 'get an AT&T access token', load POST `/oauth/v4/token`, and execute with the configured client credentials to retrieve a bearer token

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/oauth/v4/token` | Obtain or refresh an AT&T platform OAuth 2.0 access token |

## Key resources

- **OAuth** — Issue and refresh OAuth 2.0 access tokens for AT&T platform APIs via the client-credentials flow

## Why Jentic

- **Setup:** Wiring AT&T OAuth by hand means posting client_id and client_secret to the token endpoint, parsing the bearer token, and reattaching it to downstream calls yourself. Through Jentic you install once, import AT&T OAuth from the API Directory, store the client credentials once, and your agent calls it while Jentic mints and injects the token.
- **Permission scoping:** AT&T OAuth exposes a single token operation that carries its grant type and client credentials in the request body rather than a URL path, so limit the agent to the operation it needs, which is issuing a token. You choose the operations it may call, and this endpoint is the only one exposed.
- **Credential handling:** Your AT&T client_id and client_secret are stored once, encrypted, by your own Jentic One instance, which calls the token endpoint on demand and injects the resulting bearer token at execution time. Neither credential enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get an AT&T access token', and Jentic returns the POST `/oauth/v4/token` operation with its grant-type and client-credentials parameters so the call shape is correct on the first try.

## Related APIs

- **Twilio** — Programmable communications platform used as an alternative to telco-vendor APIs
- **RingCentral** — Cloud communications and contact-centre platform with its own OAuth 2.0 flow
- **Vonage Account API** — Communications platform with account and credential APIs

## FAQ

### What authentication does the AT&T OAuth API use?

The AT&T OAuth API itself implements the OAuth 2.0 client-credentials flow - callers pass client_id and client_secret to POST `/oauth/v4/token.` Through Jentic, both credentials are held in the encrypted vault and the call is made on the agent's behalf, so the secret never enters the agent's context.

### Can I refresh an AT&T access token with this API?

Yes. POST `/oauth/v4/token` supports the OAuth 2.0 token endpoint behaviour, including issuing a fresh access token with the client-credentials grant. Long-running clients re-call this endpoint before expires_in elapses to maintain valid tokens.

### What are the rate limits for the AT&T OAuth API?

AT&T throttles token-endpoint calls per client. The spec does not encode a numeric limit - the practical guidance is to refresh tokens at half the expires_in interval and avoid issuing a new token for every downstream call by caching the most recent valid token.

### How do I get an AT&T access token through Jentic?

Search Jentic for 'get an AT&T access token', load POST `/oauth/v4/token`, and execute. Jentic posts grant_type=client_credentials with the stored client_id and client_secret, then returns the access_token and expires_in to the agent.

### Is this the only AT&T API available?

This spec covers only the OAuth token endpoint, which is the gating step for the AT&T developer platform. Other AT&T platform APIs (messaging, telco services) sit behind the same OAuth flow and consume the access tokens issued here.

### Can I limit what my agent is allowed to do with the AT&T OAuth API?

Yes. The AT&T OAuth API exposes a single operation, POST `/oauth/v4/token`, which mints an access token using client-credentials passed in the request body. With your self-hosted Jentic One instance, your own rules decide which operations and credentials the agent may use, so you scope the agent to just that token-issuing call and nothing else. Because this endpoint is the only one exposed, the agent can request a token but cannot reach any other AT&T operation you have not allowed.