canonical: https://jentic.com/apis/swaggerhub.advancedcomputersoft/adastra-telephony-api

# Advancedcomputersoft Adastra Telephony API

API designed for Telephony providers to interact with Adastra. The API exposes 1 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically post caller details. Covers 1 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for media and content only.

## Capabilities

- Post caller details
- Manage media data programmatically
- Integrate Adastra Telephony API into automated workflows
- Query and filter Adastra Telephony API records by parameters
- Monitor Adastra Telephony API operational status and events

## Use cases

### Media and Content Operations

Use the Adastra Telephony API to perform media operations programmatically. The API provides 1 endpoints covering core functionality including post caller details.

Example prompt: Call POST /caller-details to post caller details

### Data Retrieval and Monitoring

Query Adastra Telephony API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Adastra Telephony API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Adastra Telephony API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'post caller details', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /caller-details | Post caller details |

## Key resources

- **Caller Details** — Caller details collected via telephony system

## Why Jentic

- **Setup:** Wiring the Adastra Telephony API by hand means setting up its OAuth2 flow and building the caller-details request yourself. Through Jentic you install once, import the Adastra Telephony API from the API Directory, store the OAuth credentials once, and your agent calls it.
- **Permission scoping:** The Telephony API exposes a single caller-details operation and takes its input in the request body, so scope by operation: limit the agent to the operations it needs, such as posting caller details. Every operation the agent can run is one you have added to its allowed set.
- **Credential handling:** Your Adastra Telephony OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'post caller details for a call', and Jentic returns the matching Adastra Telephony operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

### What authentication does the Adastra Telephony API use?

The Adastra Telephony API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I post caller details with the Adastra Telephony API?

Yes. Use the POST /caller-details endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Adastra Telephony API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I post caller details through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'post caller details'. Jentic returns the matching Adastra Telephony API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Adastra Telephony API have?

The Adastra Telephony API exposes 1 endpoints covering caller details operations.

### Can I limit what my agent is allowed to do with the Adastra Telephony API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, so you scope access by adding only the operations you want it to reach to its allowed set. The Adastra Telephony API exposes a single caller-details operation, so you can permit just POST /caller-details for posting caller details and withhold everything else. The agent can call only what you have added, and your OAuth credentials stay held by your own instance rather than in the agent context.