AT&T OAuth

Name: AT&T OAuth API
Brand: AT&T OAuth
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationoauth21 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the AT&T OAuth to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AT&T OAuth, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AT&T OAuth API.

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

GET STARTED

Start building with AT&T OAuth API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use AT&T OAuth API for, with concrete tasks.

★ 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.

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.

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.

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

1 endpoints — the at&t oauth api is the token endpoint for the at&t developer platform.

METHOD

PATH

DESCRIPTION

POST

/oauth/v4/token

Obtain or refresh an AT&T platform OAuth 2.0 access token

POST

/oauth/v4/token

Obtain or refresh an AT&T platform OAuth 2.0 access token

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AT&T client_id and client_secret are stored encrypted in the Jentic vault (MAXsystem). Jentic calls /oauth/v4/token on demand and injects the resulting bearer token into downstream AT&T API requests, so the agent never sees either credential.

Intent-based discovery

Agents search Jentic by intent (e.g. '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.

Time to first call

Direct integration: a few hours to wire the client-credentials flow, caching, and refresh. Through Jentic: a few minutes — Jentic handles issuance and rotation as part of the AT&T API call.

FAQs

Specific to using AT&T OAuth API through Jentic.

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.