Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / CRM / Hubspot / Contacts
Contacts logo

HubSpot Contacts

Browse all Hubspot APIs
✓ Official Vendor SpecCRMContact Managementoauth2,apiKey9 EndpointsREST

For Agents

Create, read, update, archive, merge, and GDPR-delete HubSpot contact records, with batch endpoints suitable for high-volume CRM sync.

Use for: I need to create a new contact record in HubSpot, Retrieve a contact by its CRM object ID, Update the lifecycle stage on an existing contact, Merge two duplicate contact records into one

Not supported: Does not handle marketing email sends, deal pipeline, or tickets — use only for HubSpot CRM contact records.

The HubSpot Contacts API manages contact records — the primary CRM object representing the people a HubSpot user does business with. It exposes the standard CRM v3 object pattern with batch read, create, update, archive, merge, and a GDPR-compliant delete endpoint against the contacts object. Each contact carries default properties such as firstname, lastname, and email, supports custom properties, and can be associated with companies, deals, and tickets.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Contacts to your agent

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

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 Contacts API.

Create contact records with email, firstname, lastname, and custom property values

Batch update contacts in groups of up to 100 records by ID

Merge two contact records into a single canonical record using the merge endpoint

GDPR-delete a contact record permanently to comply with right-to-be-forgotten requests

Retrieve a contact with associated companies, deals, and tickets in one call

Archive contacts in batch when removing from active CRM views without permanent delete

Page through all contacts with cursor-based pagination for export

Use Cases

Patterns agents use Contacts API for, with concrete tasks.

★ Lead Capture Sync

Sync newly captured leads from a marketing form or webinar platform into HubSpot as contact records. Batch create handles up to 100 contacts per request, and properties can include UTM parameters and the original lead source for attribution reporting.

POST 100 contact payloads to /crm/v3/objects/contacts/batch/create with email, firstname, lastname, and lead_source properties from the form export.

Duplicate Cleanup

When two contact records exist for the same person, merge them into a single canonical record using the merge endpoint. The merge preserves associations and activity history from both records and is non-reversible, so a dry-run pass usually precedes the merge job.

POST /crm/v3/objects/contacts/merge with primaryObjectId and objectIdToMerge to consolidate duplicate contacts into one record.

GDPR Right-to-be-Forgotten

When a contact requests deletion under GDPR, use the gdpr-delete endpoint to permanently remove the contact record and prevent recreation from synced sources. This is distinct from archive, which is reversible — gdpr-delete is the irreversible compliance action.

POST /crm/v3/objects/contacts/gdpr-delete with the contact email or id to permanently remove the contact record from HubSpot.

AI Agent Lead Routing

An AI agent reads new contacts hourly, classifies them by ICP fit using their company domain and title, and updates the lifecycle stage and owner accordingly. Jentic exposes the read and update operations with typed schemas, so the agent routes leads without consulting docs.

Read new contacts from the last hour via /crm/v3/objects/contacts, classify each, and PATCH /crm/v3/objects/contacts/{contactId} with lifecyclestage and hubspot_owner_id.

Key Endpoints

9 endpoints — the hubspot contacts api manages contact records — the primary crm object representing the people a hubspot user does business with.

METHOD

PATH

DESCRIPTION

POST

/crm/v3/objects/contacts/batch/create

Create contact records in batch

POST

/crm/v3/objects/contacts/batch/read

Read contacts in batch by ID

POST

/crm/v3/objects/contacts/batch/update

Update contact properties in batch

POST

/crm/v3/objects/contacts/batch/archive

Archive contacts in batch

POST

/crm/v3/objects/contacts/merge

Merge two contact records into one

POST

/crm/v3/objects/contacts/gdpr-delete

Permanently delete a contact for GDPR compliance

GET

/crm/v3/objects/contacts/{contactId}

Retrieve a single contact

GET

/crm/v3/objects/contacts

List contacts with pagination

POST

/crm/v3/objects/contacts/batch/create

Create contact records in batch

POST

/crm/v3/objects/contacts/batch/read

Read contacts in batch by ID

POST

/crm/v3/objects/contacts/batch/update

Update contact properties in batch

POST

/crm/v3/objects/contacts/batch/archive

Archive contacts in batch

POST

/crm/v3/objects/contacts/merge

Merge two contact records into one

POST

/crm/v3/objects/contacts/gdpr-delete

Permanently delete a contact for GDPR compliance

GET

/crm/v3/objects/contacts/{contactId}

Retrieve a single contact

GET

/crm/v3/objects/contacts

List contacts with pagination

Why Jentic?

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

Credential management

Credential isolation

HubSpot OAuth and private app tokens are encrypted in the Jentic vault. Scoped tokens are injected at execution — raw credentials never enter the agent's context or logs.

Intent-based discovery

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a hubspot contact') and Jentic returns the matching contacts operation with its typed input schema, so the agent calls the right endpoint without browsing docs.

Time to first call

Time to first call

Direct integration: 1-2 days for OAuth, batch error handling, and merge/gdpr-delete safeguards. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Companies

→

Manages company records that contacts are typically associated with.

Use Companies when the agent needs the organisation a contact belongs to; contacts and companies are usually populated together.

Complementary

Deals

→

Tracks sales opportunities associated with contact records.

Use Deals when the agent needs to attach a contact to a sales pipeline opportunity.

Alternative

Salesforce

→

Salesforce Lead and Contact objects are the equivalent person records at enterprise scale.

Choose Salesforce when the host organisation standardises on Salesforce Leads/Contacts rather than HubSpot.

FAQs

Specific to using Contacts API through Jentic.

What authentication does the HubSpot Contacts API use?

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

Can I merge duplicate contacts with the HubSpot Contacts API?

Yes — POST /crm/v3/objects/contacts/merge with primaryObjectId and objectIdToMerge in the request body. Associations and activity history from the merged record transfer to the primary record. The operation is not reversible.

What are the rate limits for the HubSpot Contacts API?

Standard CRM v3 limits apply — 100 requests per 10 seconds for OAuth apps and 110 per 10 seconds for private apps on Pro and Enterprise. Use /crm/v3/objects/contacts/batch/create or /batch/update (up to 100 records per call) when syncing large lead lists.

How do I GDPR-delete a contact through Jentic?

Run the Jentic search "gdpr delete hubspot contact" to find POST /crm/v3/objects/contacts/gdpr-delete, load the schema, and execute with the contact email or id. Jentic handles authentication. This is irreversible — confirm before running.

Is the HubSpot Contacts API free?

The Contacts API is included with any HubSpot account, including the free tier. There is no per-call HubSpot fee, but custom property limits and higher API throughput require a paid tier.

Can I associate a contact with a company and deal in one call?

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

GET STARTED

Start building with Contacts API

Explore with Jentic
View OpenAPI Document