canonical: https://jentic.com/apis/objectionly.com/objectionly

# Objectionly API

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. The public API exposes a single endpoint that queues a call for processing, accepting workspace and proxy credentials so partners can submit transcripts on behalf of their accounts. It suits sales operations teams that want to bring Objectionly's objection tagging into an automated post-call pipeline.

## For AI agents

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

## Scope

Does not host meeting recordings, transcribe audio from raw files, or expose coaching insights through this API surface - use for queuing calls into Objectionly's processing pipeline only.

## Capabilities

- 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
- Bridge meeting recording tools to Objectionly without manual upload
- Trigger Objectionly's coaching pipeline immediately after a call ends

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/call-processing/queue` | Queue a sales call for processing by Objectionly |

## Key resources

- **Call Processing** — Queue a call for objection tagging and coaching analysis

## Why Jentic

- **Setup:** Wiring the Objectionly API by hand means managing a workspace API key plus the X-Objectionly-Proxy-Token, adding both headers to every call against api.objectionly.com, and coding your own retry handling. Through Jentic you install once, import the Objectionly API from the API Directory, store both once, and your agent calls it.
- **Permission scoping:** Objectionly exposes a single operation that queues calls into its processing pipeline, so scope it by operation: limit the agent to that queue call and nothing else. You choose which operations it may call, so no other behaviour runs unless you add it.
- **Credential handling:** Your workspace API key and X-Objectionly-Proxy-Token are stored once, encrypted, by your own Jentic One instance and injected as headers at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'queue a sales call for analysis', and Jentic returns the POST `/api/call-processing/queue` operation with its input schema so the agent calls it correctly without reading the Objectionly docs.

## Related APIs

- **Gong API** — Full revenue intelligence platform - covers call recording, transcription, and analytics rather than queuing into a separate analysis service
- **Chorus.ai API** — Conversation intelligence with built-in recording and analytics - broader feature set than Objectionly's queue endpoint
- **Salesloft API** — Sales engagement workflows that can trigger calls - pair with Objectionly to analyse the resulting recordings

## FAQ

### 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 your Jentic One instance 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.

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

Yes. The Objectionly API exposes a single operation, POST `/api/call-processing/queue`, which queues a sales call for objection tagging and coaching analysis. Because you run Jentic One yourself and your own rules decide which operations and credentials an agent may use, you can allow only this queue call and nothing else, so the agent cannot reach any other behaviour unless you add it. Your workspace API key and proxy token are supplied at execution time under those rules rather than being handed to the agent directly.