Call Control API
★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey6 EndpointsREST
For Agents
Look up the spam reputation of a phone number, check complaints, and decide whether to block an inbound caller for an enterprise user via the Call Control API.
Use for: I need to check the reputation of an inbound phone number, Find out whether a number has been reported as spam, Get the complaint history for a phone number, Decide whether to block a specific caller for a specific user
Not supported: Does not handle outbound call placement, SMS sending, or call recording — use for phone number reputation lookups and spam block decisions only.
Jentic publishes the only available OpenAPI specification for the Call Control API, keeping it validated and agent-ready. Call Control returns reputation and block decisions for phone numbers using a crowdsourced blacklist drawn from 12+ million end users and US government feeds (FTC, FCC, IRS). Six endpoints cover number reputation lookups, complaint history, per-user block decisions for enterprise tenants, user upsert, and report submission. Authentication is an apiKey header on every request, and the API is intended for telephony platforms, contact centres, and agent tools that need to filter likely spam or fraud calls before they reach a human.
Install Jentic One Beta
Connect the Call Control API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Call Control 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 Call Control API.
Look up reputation scores for any phone number via /api/2015-11-01/Reputation/{phoneNumber}
Retrieve complaint history for a number via /api/2015-11-01/Complaints/{phoneNumber}
Decide whether to block a caller for a specific user via the Enterprise ShouldBlock endpoint
Upsert enterprise user profiles to drive per-user block decisions
Submit user-reported spam back to Call Control via /api/2015-11-01/Report
Authenticate every request with the apiKey header
Use Cases
Patterns agents use Call Control API for, with concrete tasks.
★ Inbound Caller Screening
When a call hits the contact centre, the call router calls Reputation/{phoneNumber} to retrieve the spam score and complaint count, then chooses whether to send the caller straight to voicemail or to a live agent. The data is sourced from a blacklist of 12+ million users plus FTC, FCC, and IRS feeds, so coverage of US robocallers is strong.
GET /api/2015-11-01/Reputation/{phoneNumber} for the inbound number and route the call based on the reputation score.
Per-User Block Decision
For enterprise tenants where each end user has their own block preferences, call Enterprise/ShouldBlock/{phoneNumber}/{userPhoneNumber} to get a block-or-allow decision tailored to that user. The endpoint takes both the inbound caller number and the recipient user number, so personal whitelists and the global community blacklist are combined automatically.
GET /api/2015-11-01/Enterprise/ShouldBlock/{phoneNumber}/{userPhoneNumber} and reject the call when the response indicates block.
User-Reported Spam Feedback Loop
When an end user marks a call as spam in the company app, POST that report to /api/2015-11-01/Report so the data flows back into the Call Control crowdsourced blacklist. This both improves global signal quality and ensures that a number flagged by your users is also treated as spam in future Reputation checks.
POST a Report payload to /api/2015-11-01/Report containing the phone number, reporter user ID, and category of spam.
Enterprise User Onboarding
When provisioning new users on a corporate phone system, call Enterprise/UpsertUser to register their phone number with Call Control. After the upsert, the ShouldBlock endpoint can return per-user block decisions for that user, and GetUser can look up the enterprise user by phone number for diagnostics.
POST the new user's phone number and metadata to /api/2015-11-01/Enterprise/UpsertUser, then verify with GET /api/2015-11-01/Enterprise/GetUser/{phoneNumber}.
AI Agent Caller Reputation Lookup via Jentic
Through Jentic, an AI agent searches for an intent like 'check the reputation of this phone number' and is returned the Reputation operation along with its input schema. The agent passes the phone number from the inbound webhook, gets the score, and decides whether to escalate to a human or auto-respond. Setup time is under an hour rather than several days of direct integration.
Use Jentic search for 'check the reputation of a phone number', load the Reputation schema, and execute it with the inbound phone number.
Key Endpoints
6 endpoints — jentic publishes the only available openapi specification for the call control api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/api/2015-11-01/Reputation/{phoneNumber}
Look up the reputation of a phone number
GET
/api/2015-11-01/Complaints/{phoneNumber}
Retrieve complaint history for a number
GET
/api/2015-11-01/Enterprise/ShouldBlock/{phoneNumber}/{userPhoneNumber}
Per-user block decision
GET
/api/2015-11-01/Enterprise/GetUser/{phoneNumber}
Look up an enterprise user by phone number
POST
/api/2015-11-01/Enterprise/UpsertUser
Create or update an enterprise user
POST
/api/2015-11-01/Report
Submit a spam report from a user
GET
/api/2015-11-01/Reputation/{phoneNumber}
Look up the reputation of a phone number
GET
/api/2015-11-01/Complaints/{phoneNumber}
Retrieve complaint history for a number
GET
/api/2015-11-01/Enterprise/ShouldBlock/{phoneNumber}/{userPhoneNumber}
Per-user block decision
GET
/api/2015-11-01/Enterprise/GetUser/{phoneNumber}
Look up an enterprise user by phone number
POST
/api/2015-11-01/Enterprise/UpsertUser
Create or update an enterprise user
POST
/api/2015-11-01/Report
Submit a spam report from a user
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Call Control apiKey header value is stored encrypted in the Jentic vault. Agents call Reputation, ShouldBlock, and Report by name and Jentic injects the apiKey header at execution time — the raw key never enters the agent prompt or logs.
Intent-based discovery
Agents search Jentic by intent (for example 'check the reputation of a phone number' or 'should I block this caller') and Jentic returns the matching Call Control operation along with its input schema, so the agent can call the right endpoint without browsing Call Control documentation.
Time to first call
Direct Call Control integration: 1-2 days for apiKey wiring, per-endpoint response handling, and feedback loop wiring for /Report. Through Jentic: under 1 hour — search for the operation, load its schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Call Control API through Jentic.
Why is there no official OpenAPI spec for the Call Control API?
Call Control publishes a Swagger JSON on their marketing site but does not host a maintained OpenAPI specification on a developer portal. Jentic generates and maintains this spec so that AI agents and developers can call the Call Control API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Call Control API use?
The Call Control API uses an API key passed in the apiKey HTTP header. Through Jentic, the key is stored encrypted in the credential vault and injected at execution time, so the agent never holds the raw value in its context.
Can I check whether a specific caller should be blocked for a specific user?
Yes. Call /api/2015-11-01/Enterprise/ShouldBlock/{phoneNumber}/{userPhoneNumber} with both the inbound caller number and the recipient user number. The endpoint combines the user's personal block preferences with the global crowdsourced blacklist.
What are the rate limits for the Call Control API?
The OpenAPI specification does not declare per-endpoint rate limits. Limits are tied to the enterprise contract — contact Call Control for the throughput agreed for your apiKey before scheduling high-volume reputation sweeps.
How do I look up the reputation of a phone number through Jentic?
Run a Jentic search for 'check the reputation of a phone number', load the Reputation schema, and execute it with the inbound phone number. Install the SDK with pip install jentic and use the async search, load, and execute pattern.
Is the Call Control API free?
Call Control prices the API for enterprise customers rather than offering a public free tier. Pricing is not declared in the OpenAPI spec and depends on call volume and the endpoints enabled — contact Call Control sales for current rates.
GET STARTED