Official vendor OpenAPI document · agent-readyCRMContact 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.
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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-crm-contacts" | sh2
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-contacts" | 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 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
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
Contacts
- Foundational (D-)42/100
72
Foundational Compliance63
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience94
Agent Usability70
Security61
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
72
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
89%
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
9%
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.
18
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
19%
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.
52%
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).
61
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
61%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the HubSpot Contacts API by hand means handling its OAuth 2.0 authorization-code flow or a private app token, targeting api.hubapi.com, and building batch, merge, and GDPR-delete payloads yourself. Through Jentic you install once, import HubSpot Contacts 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 contact scopes your agent needs and you choose which operations it may call: you can allow reading and updating contact records while leaving destructive operations like merge, archive, or GDPR delete 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 'create a HubSpot contact' or 'read a contact by id', and Jentic returns the matching contacts 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.
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.
Can I limit what my agent is allowed to do with the HubSpot Contacts API?
Yes. Because you run Jentic One yourself, your own rules decide which contact operations and credentials the agent may use, and HubSpot's per-object OAuth scopes let you grant only the access it needs. For example, you can allow reading and updating contact records while leaving destructive operations like merge, batch archive, and GDPR delete out of the allowed set. The agent can only call the operations you explicitly permit.
GET STARTED