Advancedcomputersoft Adastra Telephony API
Browse all Swaggerhub Advancedcomputersoft APIs★ Only Publicly Available OpenAPI DocumentMediaImage Processingoauth21 EndpointsREST
For Agents
Programmatically post caller details. Covers 1 operations with oauth2 authentication.
Use for: I need to post caller details, Find available media operations, Get the current status of Adastra Telephony API resources, List all records from Adastra Telephony API
Not supported: Does not handle payments, communications, or crm — use for media and content only.
API designed for Telephony providers to interact with Adastra. The API exposes 1 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the Adastra Telephony API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adastra Telephony API, 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.
1
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 | sh2
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 instanceJentic 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 Adastra Telephony API.
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
Patterns agents use Adastra Telephony API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'post caller details', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
1 endpoints — api designed for telephony providers to interact with adastra.
METHOD
PATH
DESCRIPTION
POST
/caller-details
Post caller details
POST
/caller-details
Post caller details
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Adastra Telephony API oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'post caller details') and Jentic returns the matching Adastra Telephony API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Adastra Telephony API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Adastra Telephony API through Jentic.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED