Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / CRM / Hubspot / Calls
Calls logo

HubSpot Calls

Browse all Hubspot APIs
45
AI ReadinessFoundational (D)45/100
See full scorecard
Official vendor OpenAPI document · agent-readyCRMContact Managementoauth2,apiKey11 EndpointsREST

For Agents

Create, read, update, archive, search, and upsert HubSpot CRM call engagement records, with batch endpoints for high-volume telephony logging.

Use for: I need to log a new call engagement in HubSpot CRM, Retrieve a call record by its engagement ID, Search for all calls made to a specific contact in the last 30 days, Update the outcome and notes on a completed call

Not supported: Does not place calls, host recordings, or transcribe audio - use only for managing HubSpot CRM call engagement records.

The HubSpot Calls API manages call engagement records in the CRM - the structured log of inbound and outbound calls associated with contacts, companies, and deals. It exposes batch CRUD plus search and upsert against the calls object using the standard CRM v3 object pattern. Each call record can carry properties such as duration, call direction, recording URL, notes, and outcome, and can be associated with other CRM objects.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Calls to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Calls, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-crm-calls" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-crm-calls" | 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 Calls API.

Create call engagement records with direction, duration, recording URL, and outcome properties

Batch upsert call records by an idempotency key to avoid duplicates from retried telephony events

Search call records by contact, company, date range, or call outcome using filter groups

Retrieve a call engagement by ID with associated contacts, companies, and deals

Update call properties (notes, disposition) after the call ends

Archive call records in batch when removing them from active CRM views

Page through all call records with cursor-based pagination for export jobs

Use Cases

Patterns agents use Calls API for, with concrete tasks.

★ Telephony Activity Logging

When a sales rep finishes a call in their dialer, the integration logs it as a call engagement in HubSpot so the rep's manager can see activity against the contact and deal. Batch create handles up to 100 calls per request, suitable for daily reconciliation jobs from the telephony platform.

POST 50 call records to /crm/v3/objects/calls/batch/create with hs_call_direction, hs_call_duration, and contact associations from the dialer export.

Call Outcome Reporting

Search call records filtered by outcome and date range to drive a weekly sales effectiveness dashboard. The search endpoint supports paging, sorting, and property selection, so the report only pulls the columns it needs.

Search /crm/v3/objects/calls/search with filterGroups for hs_call_disposition equals "Connected" and hs_timestamp in the last 7 days, returning hs_call_duration and ownerId.

Idempotent Call Upsert

Use batch upsert with an external telephony id as the idempotency key so retried webhooks from the telephony provider do not create duplicate call engagements. This pattern is critical when the provider retries on network failures.

POST to /crm/v3/objects/calls/batch/upsert with idProperty set to hs_unique_creation_key and 100 call payloads from the provider's queue.

AI Agent Call Enrichment

An AI agent reads the latest call recordings, summarises them with an LLM, and writes the summary plus disposition back to the HubSpot call record. Jentic exposes the search and update operations with typed schemas, so the agent updates the right field without consulting docs.

Search calls in the last 24h missing hs_call_body, fetch each recording, generate a summary, then PATCH /crm/v3/objects/calls/{callId} with the summary and disposition.

Key Endpoints

11 endpoints — the hubspot calls api manages call engagement records in the crm - the structured log of inbound and outbound calls associated with contacts, companies, and deals.

METHOD

PATH

DESCRIPTION

POST

/crm/v3/objects/calls/batch/create

Create call engagements in batch

POST

/crm/v3/objects/calls/batch/upsert

Idempotent upsert by external id

POST

/crm/v3/objects/calls/batch/read

Read calls in batch by ID

POST

/crm/v3/objects/calls/batch/update

Update call properties in batch

POST

/crm/v3/objects/calls/search

Search calls by filter groups

GET

/crm/v3/objects/calls/{callId}

Retrieve a single call engagement

GET

/crm/v3/objects/calls

List calls with pagination

POST

/crm/v3/objects/calls/batch/create

Create call engagements in batch

POST

/crm/v3/objects/calls/batch/upsert

Idempotent upsert by external id

POST

/crm/v3/objects/calls/batch/read

Read calls in batch by ID

POST

/crm/v3/objects/calls/batch/update

Update call properties in batch

POST

/crm/v3/objects/calls/search

Search calls by filter groups

GET

/crm/v3/objects/calls/{callId}

Retrieve a single call engagement

GET

/crm/v3/objects/calls

List calls with pagination

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

C

Calls

- Foundational (D)
45/100
74
Foundational Compliance
63
Developer Experience & Jentic Compatibility
20
AI-Readiness & Agent Experience
94
Agent Usability
70
Security
78
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4
8%

Example Density

How richly the API is illustrated with examples.

95%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

20

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
20%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

70

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1
70%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

78

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the HubSpot Calls API by hand means handling its OAuth 2.0 authorization-code flow or a private app token, targeting api.hubapi.com, and coding batch and search request shapes yourself. Through Jentic you install once, import HubSpot Calls from the API Directory, store the token once, and your agent calls it.

Permission scoping

HubSpot gates this API with per-object OAuth scopes, so you grant only the call-engagement scopes your agent needs and you choose which operations it may call: you can allow reading and searching call records while leaving batch updates out of the allowed set unless you add them.

Credential isolation

Your HubSpot OAuth token or private app 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 'log a call in HubSpot' or 'find recent call records', and Jentic returns the matching calls operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

CRM Calling Extensions

→

Registers the calling app that creates these call engagement records inside HubSpot.

Use Calling Extensions to register the dialer app, then use Calls to write engagement records during and after calls.

Complementary

Contacts

→

Standard CRM contact object that calls are typically associated with.

Use Contacts to look up or update the contact a call should be associated with before creating the call engagement.

Alternative

Twilio

→

Twilio Voice exposes raw call records and recordings without the CRM activity layer.

Choose Twilio when the agent only needs the telephony record and is not maintaining a CRM activity timeline.

FAQs

Specific to using Calls API through Jentic.

What authentication does the HubSpot Calls API use?

The Calls API supports OAuth 2.0 (oauth2 and oauth2_legacy) and HubSpot private app tokens. Through Jentic, tokens are stored in the vault and a scoped token is injected per request, so raw credentials never enter the agent context.

Can I attach a call recording URL with the HubSpot Calls API?

Yes - set the hs_call_recording_url property on create or update. HubSpot stores the URL on the engagement and surfaces a player in the CRM timeline. The recording itself is hosted by your telephony provider; HubSpot does not re-upload the audio.

What are the rate limits for the HubSpot Calls API?

Standard CRM API limits apply - 100 requests per 10 seconds for OAuth apps and 110 per 10 seconds for private apps. Use /crm/v3/objects/calls/batch/create or /batch/upsert (up to 100 records per request) to stay under the limit during bulk syncs.

How do I upsert calls through Jentic?

Run the Jentic search "upsert hubspot call records" to find POST /crm/v3/objects/calls/batch/upsert, load its schema, and execute with idProperty set to a unique external id. Jentic handles authentication and returns per-record success or error.

Is the HubSpot Calls API free?

The Calls API is included with any HubSpot account that has Sales Hub or Service Hub enabled. There is no per-call API charge from HubSpot beyond the underlying tier subscription.

Can I associate a call with multiple contacts?

Yes - pass an associations array on create, or use the CRM Associations API afterwards, to link a single call engagement to multiple contacts, companies, and deals. The single-record GET supports an associations parameter to return linked IDs in one call.

Can I limit what my agent is allowed to do with the HubSpot Calls API?

Yes. Because Jentic One is self-hosted, you decide which of the HubSpot Calls operations your agent may call and which OAuth scopes back them, so your own rules govern access to the call-engagement object. HubSpot gates this API with per-object scopes, so you can grant only the call-engagement scopes the agent needs and, for example, allow it to read and search call records while leaving batch create, update, and upsert out of the allowed set. Your HubSpot token is held by your own instance and injected only for the operations you have permitted.

GET STARTED

Start building with Calls API

Explore with Jentic One
View OpenAPI Document