Advancedcomputersoft Adastra IVR API

Name: Adastra IVR API
Brand: Adastra IVR API
Availability: InStock

Browse all Swaggerhub Advancedcomputersoft APIs

★ Only Publicly Available OpenAPI DocumentHealthcareAppointment Schedulingbearer3 Endpoints

Install Jentic One Beta

Connect the Adastra IVR API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adastra IVR 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.

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 Adastra IVR API.

Obtain JWT token

Get patient details

Create case

Query and filter Adastra IVR API records by parameters

GET STARTED

Start building with Adastra IVR API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Adastra IVR API for, with concrete tasks.

★ Healthcare Operations

Use the Adastra IVR API to perform healthcare operations programmatically. The API provides 3 endpoints covering core functionality including obtain jwt token, get patient details, create case.

Call POST /authenticate to obtain jwt token

Automated Authentication Management

Automate authentication operations by combining multiple Adastra IVR API endpoints. Agents can get patient details and then create case in a single workflow.

Call POST /patient-search to get patient details, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Adastra IVR 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 bearer tokens manually.

Search Jentic for 'obtain jwt token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — introduction the api provides option to search for a patient based on the phone number and the date of birth and create a case if the details match.

METHOD

PATH

DESCRIPTION

POST

/authenticate

Obtain JWT token

POST

/patient-search

Get patient details

POST

/cases

Create case

POST

/authenticate

Obtain JWT token

POST

/patient-search

Get patient details

POST

/cases

Create case

Why Jentic?

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

Credential isolation

Your Adastra IVR bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'obtain a JWT token' or 'search for a patient', and Jentic returns the matching Adastra IVR operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Adastra IVR API through Jentic.

What authentication does the Adastra IVR API use?

The Adastra IVR API uses a Bearer token in the Authorization header. 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 obtain jwt token with the Adastra IVR API?

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

What are the rate limits for the Adastra IVR 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 obtain jwt token through Jentic?

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

How many endpoints does the Adastra IVR API have?

The Adastra IVR API exposes 3 endpoints covering authentication, patient, case operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Adastra IVR operations and credentials the agent may use. Since this API passes its targets in the request body rather than the URL path, you scope by operation: add only what the agent needs, such as POST /authenticate for a JWT token and POST /patient-search to look up a patient. Case creation via POST /cases is available to the agent only if you add it to the allowed set.

Advancedcomputersoft Adastra IVR API

Connect the Adastra IVR API to your agent

Capabilities

Start building with Adastra IVR API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs