Objectionly API

Name: Objectionly API
Brand: Objectionly API
Availability: InStock

✓ Official Vendor SpecCRMCustomer SuccessapiKey1 EndpointsREST

For Agents

Queue a sales call recording or transcript with Objectionly so it is processed for objection tagging and coaching insights.

Install Jentic One Beta

Connect the Objectionly API to your agent

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

Queue a sales call for objection tagging and coaching analysis

Submit calls on behalf of a workspace using a workspace API key

Authenticate proxied submissions with an Objectionly proxy token

GET STARTED

Start building with Objectionly API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Objectionly API for, with concrete tasks.

★ Automated post-call processing pipeline

Bridge a meeting recording tool to Objectionly by calling POST /api/call-processing/queue at the end of each sales call. The endpoint accepts the call payload along with the workspace API key, so an integration worker can submit hundreds of calls per day without manual upload. Sales managers see objection tags and coaching insights inside Objectionly the next time they open the call.

Listen for a 'recording.completed' webhook from the meeting tool, then POST /api/call-processing/queue with the recording URL and the workspace API key

CRM-triggered call analysis

Trigger Objectionly call processing from CRM events such as opportunity stage changes by mapping the relevant call record into the queue endpoint. Revenue ops teams can use this to make sure every late-stage call gets coaching analysis without relying on individual reps to push the button. Submissions complete in a single POST so the CRM workflow stays simple.

On a CRM 'Opportunity moved to Negotiation' event, POST /api/call-processing/queue with the latest call recording for the opportunity

Partner-side submission via proxy token

Build a partner integration that submits calls into multiple Objectionly workspaces using the X-Objectionly-Proxy-Token header alongside the workspace API key. Recording-platform partners can offer one-click Objectionly handoff for their joint customers without the customer needing to wire a direct integration. The single queue endpoint keeps the partner surface area small.

POST /api/call-processing/queue with X-Objectionly-Proxy-Token and the customer's X-Workspace-API-Key to submit on the customer's behalf

AI agent integration via Jentic

A revenue operations agent searches Jentic for sales call analysis, loads the POST /api/call-processing/queue schema, and queues each new call recording for Objectionly to process. The agent watches a meeting tool inbox, identifies new calls, and submits them with the workspace API key Jentic injects. Coaching insights appear in Objectionly for the manager to review.

Use Jentic to search 'queue sales call for analysis', load POST /api/call-processing/queue, and execute it with each new recording from the meeting tool inbox

Key Endpoints

1 endpoints — objectionly is a sales call analysis tool that imports meeting transcripts, tags objections raised by prospects, scores calls, and surfaces coaching insights for sales managers.

METHOD

PATH

DESCRIPTION

POST

/api/call-processing/queue

Queue a sales call for processing by Objectionly

POST

/api/call-processing/queue

Queue a sales call for processing by Objectionly

Why Jentic?

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

Credential isolation

Workspace API keys and the X-Objectionly-Proxy-Token are stored encrypted in the Jentic vault (MAXsystem). At execution time Jentic injects both headers into the call so the agent never sees the raw secrets in its prompt or logs.

Intent-based discovery

Agents search Jentic with intents like 'queue sales call for analysis' and Jentic returns POST /api/call-processing/queue with its parameter schema, so the agent can call the operation correctly without reading the Objectionly docs.

Time to first call

Direct integration: half a day to handle the dual-header auth and the queue payload. Through Jentic: under an hour to discover the operation, load the schema, and queue the first call.

FAQs

Specific to using Objectionly API through Jentic.

What authentication does the Objectionly API use?

Calls to POST /api/call-processing/queue require the X-Workspace-API-Key header, and partner submissions also send X-Objectionly-Proxy-Token. Through Jentic, both headers are populated from credentials stored in the Jentic vault (MAXsystem) at execution time, so neither the workspace key nor the proxy token enters the agent's prompt context.

Can I queue a sales call for Objectionly to analyse via the API?

Yes. POST /api/call-processing/queue accepts the call submission payload defined in the spec and returns an acknowledgement. Once queued, Objectionly processes the call asynchronously and the resulting objection tags and coaching insights become available in the workspace UI.

How does the proxy token differ from the workspace API key?

The X-Workspace-API-Key identifies which Objectionly workspace the call belongs to, while X-Objectionly-Proxy-Token authenticates a partner that is submitting on behalf of that workspace. Direct customer integrations only need the workspace key; recording-platform partners building a one-click Objectionly handoff use both headers.

What are the rate limits for the Objectionly API?

The OpenAPI spec does not publish explicit rate limits. Objectionly applies workspace-level limits that depend on your plan; check your account or contact Objectionly support for figures. Through Jentic, the agent loop can pace calls so a backfill run does not breach the workspace allowance.

How do I queue a call into Objectionly through Jentic?

Install the SDK with pip install jentic, search 'queue sales call for analysis', load POST /api/call-processing/queue, and execute it with the call payload. Jentic injects the workspace API key (and proxy token if configured) so the agent code does not handle the secrets directly.

Does the Objectionly API expose tagged objections or call scores?

Not in this API surface. The published endpoint queues calls for processing; the resulting objections, scores, and coaching insights are surfaced inside the Objectionly app rather than via a public read endpoint. If you need programmatic read access, contact Objectionly to confirm whether additional endpoints are available on your plan.