Official vendor OpenAPI document · agent-readyCRMContact Managementoauth2,apiKey11 EndpointsREST
For Agents
Read, create, update, archive, and search any standard or custom HubSpot CRM record through generic object-type endpoints, with batch operations for bulk record changes.
Use for: I need to look up a CRM record by object type and ID, Create a batch of CRM records of a custom object type, Search for records that match a set of property filters, List all records of a specific object type with pagination
Not supported: Does not handle marketing email sends, workflow automation, or analytics reporting - use for generic CRM record CRUD and search only.
The HubSpot CRM Objects API provides a unified interface for reading, creating, updating, and archiving any standard or custom CRM record by object type. It exposes generic endpoints that operate against companies, contacts, deals, line items, products, tickets, quotes, and any custom object you define on the portal. Batch read, create, update, and archive operations let agents move large volumes of records in a single call, and a search endpoint supports filtering and pagination across object types. Use it as the primary CRUD layer when you need a single integration that works across HubSpot's full object model rather than a separate client for each record type.
Install Jentic One Beta
Connect the CRM Objects to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CRM Objects, 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-objects" | 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-objects" | 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 CRM Objects API.
Read any CRM record by object type and record ID without using a type-specific client
Create, update, or archive records in batches of up to 100 with batch endpoints
Search records of any object type using filter groups, sort criteria, and pagination
List records of a given object type with property selection and association expansion
Patch individual records to update specific properties without overwriting others
Operate against custom object types defined in the HubSpot portal using the same endpoints
Use Cases
Patterns agents use CRM Objects API for, with concrete tasks.
★ Unified CRUD across standard and custom objects
Treat companies, contacts, deals, custom objects, and any other CRM record through the same generic endpoints. Pass the object type as a path parameter and reuse the same code path for read, list, patch, and archive operations. This removes the need to build a separate integration per record type and is the recommended approach when an agent has to operate over HubSpot's full object graph.
Fetch the record at /crm/v3/objects/{objectType}/{objectId} for objectType=companies and objectId=12345 and return its properties.
Bulk record migration
Migrate large volumes of records into HubSpot using the batch create endpoint, then verify the import with batch read. The batch endpoints accept up to 100 records per call, which makes them suitable for ETL pipelines, CSV imports, and inter-system syncs. Pair this with the search endpoint to validate the import landed.
POST 100 contact records to /crm/v3/objects/contacts/batch/create and confirm each one returned a non-null id field.
Conditional record search
Run filtered searches across any object type using filter groups, sorts, and a query string. The search endpoint returns paginated results with the standard CRM properties and supports filtering on custom properties. Useful for agents that need to locate records matching multi-property criteria before acting on them.
POST a search to /crm/v3/objects/companies/search filtering where industry equals SOFTWARE and lifecyclestage equals customer, sorted by createdate descending.
AI agent execution through Jentic
An agent that needs to act on HubSpot records discovers this API through Jentic's intent search using a query like 'read a hubspot crm record', loads the input schema for /crm/v3/objects/{objectType}/{objectId}, and executes the call with credentials supplied from your Jentic One instance. The same flow works for batch operations and search.
Search Jentic for 'read a hubspot crm record', load the GET /crm/v3/objects/{objectType}/{objectId} operation, and execute it for objectType=deals and objectId=987.
Key Endpoints
11 endpoints — the hubspot crm objects api provides a unified interface for reading, creating, updating, and archiving any standard or custom crm record by object type.
METHOD
PATH
DESCRIPTION
GET
/crm/v3/objects/{objectType}/{objectId}
Read a single record by object type and ID
PATCH
/crm/v3/objects/{objectType}/{objectId}
Update properties on a single record
DELETE
/crm/v3/objects/{objectType}/{objectId}
Archive a single record
GET
/crm/v3/objects/{objectType}
List records of an object type with pagination
POST
/crm/v3/objects/{objectType}/batch/create
Create up to 100 records in one call
POST
/crm/v3/objects/{objectType}/batch/read
Read up to 100 records by ID in one call
POST
/crm/v3/objects/{objectType}/batch/update
Update up to 100 records in one call
POST
/crm/v3/objects/{objectType}/batch/archive
Archive up to 100 records in one call
GET
/crm/v3/objects/{objectType}/{objectId}
Read a single record by object type and ID
PATCH
/crm/v3/objects/{objectType}/{objectId}
Update properties on a single record
DELETE
/crm/v3/objects/{objectType}/{objectId}
Archive a single record
GET
/crm/v3/objects/{objectType}
List records of an object type with pagination
POST
/crm/v3/objects/{objectType}/batch/create
Create up to 100 records in one call
POST
/crm/v3/objects/{objectType}/batch/read
Read up to 100 records by ID in one call
POST
/crm/v3/objects/{objectType}/batch/update
Update up to 100 records in one call
POST
/crm/v3/objects/{objectType}/batch/archive
Archive up to 100 records in one call
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
CRM Objects
- Foundational (D-)41/100
72
Foundational Compliance64
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience94
Agent Usability63
Security59
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.
64
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
7%
Example Density
How richly the API is illustrated with examples.
100%
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
18%
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.
53%
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.
63
Security
Trust, risk posture, and security compliance.
Grade: BSignals: 1
63%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
59
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C+Signals: 1
59%
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 CRM Objects by hand means implementing HubSpot's OAuth2 authorization-code flow (or managing a private-app header token), sending each call to api.hubapi.com with the correct objectType in the path and matching property payloads, and handling token refresh yourself. Through Jentic you install once, import CRM Objects from the API Directory, store the token once, and your agent calls it.
Permission scoping
This API puts the object type in the URL path (/crm/v3/objects/{objectType}/...), so a rule can pin your agent to one object type: it can read and search records of that type and no other. You choose the operations it may call, so destructive ones like record delete or batch archive are not included unless you add them.
Credential isolation
Your HubSpot 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 'read a HubSpot CRM record' or 'batch create records', and Jentic returns the matching CRM Objects 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 CRM Objects API through Jentic.
What authentication does the HubSpot CRM Objects API use?
It accepts OAuth 2.0 access tokens issued to a HubSpot app and private app access tokens passed as a Bearer token in the Authorization header. Through Jentic, the token is stored in the credential vault and injected at execution time, so the raw token never enters the agent's prompt context.
Can I work with custom objects through this API?
Yes. The same endpoints under /crm/v3/objects/{objectType} accept any custom object type defined on the portal in addition to standard types like companies and contacts, so a single integration covers the whole object model.
What are the rate limits for the HubSpot CRM Objects API?
HubSpot enforces account-level rate limits that vary by subscription tier (typically 100 requests per 10 seconds for OAuth apps and higher daily caps for Enterprise). Batch endpoints count as a single request, so prefer /crm/v3/objects/{objectType}/batch/create over per-record loops to stay within limits.
How do I create a batch of records through Jentic?
Search Jentic with 'batch create hubspot records', load the POST /crm/v3/objects/{objectType}/batch/create operation, then execute it with an inputs array of up to 100 records. Jentic returns the response body containing each created record's id and properties.
Is the HubSpot CRM Objects API free?
It is included with every HubSpot account that has API access enabled. The free tier includes lower rate limits and standard objects only; custom object endpoints require an Enterprise subscription.
How do I update properties on a record without overwriting others?
Use PATCH /crm/v3/objects/{objectType}/{objectId} with a properties object that contains only the fields you want to change. Properties not included in the request body remain untouched on the record.
Can I limit what my agent is allowed to do with the HubSpot CRM Objects API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Since this API carries the object type in the URL path (/crm/v3/objects/{objectType}/...), you can pin the agent to a single object type so it only reads and searches records of that type and no other. You also choose which operations it may call, so destructive ones like DELETE /crm/v3/objects/{objectType}/{objectId} or POST /crm/v3/objects/{objectType}/batch/archive stay out of reach unless you explicitly grant them.
GET STARTED