Official vendor OpenAPI document · agent-readyE CommerceStorefrontoauth2,apiKey11 EndpointsREST
For Agents
Manage the HubSpot product catalogue with create, read, update, archive, and search across single records and batches of up to 100 products.
Use for: I need to seed a HubSpot portal with products from our PIM, Find a product by SKU, Update the price on a list of products, List all products in the catalogue
Not supported: Does not manage inventory levels, fulfilment, or storefront rendering - use for HubSpot CRM product catalogue records only.
The HubSpot CRM Products API manages the product catalogue inside a HubSpot portal - the master list of products that quotes, deals, and orders reference through line items. It supports the full CRM object pattern: read, list, patch, and archive single products, plus batch read, create, update, and archive of up to 100 products per call, and a search endpoint with filter groups and sort. Use it to seed a HubSpot portal from an external product database, keep prices and SKUs in sync with an upstream system of record, and build product pickers inside sales tools that talk straight to the live catalogue.
Install Jentic One Beta
Connect the Products to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Products, 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-products" | 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-products" | 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 Products API.
Create a product with name, SKU, price, and custom properties
Read a product record by ID with property selection
Update product properties such as price or description without overwriting unrelated fields
List products with cursor-based pagination
Search products by SKU, price range, or any custom property
Batch create, update, read, or archive up to 100 products per call
Use Cases
Patterns agents use Products API for, with concrete tasks.
★ Catalogue sync from a PIM
Keep the HubSpot product catalogue in lockstep with an upstream Product Information Management system. Use POST /crm/v3/objects/products/batch/create for new SKUs, POST /crm/v3/objects/products/batch/update for price and description changes, and POST /crm/v3/objects/products/batch/archive for discontinued items. Each call handles up to 100 products and the search endpoint can verify the change landed.
POST 100 products to /crm/v3/objects/products/batch/create with name, hs_sku, and price properties, and verify each returned a non-null id.
Price update across SKUs
Run a bulk price update - for example a quarterly list-price refresh - across hundreds of products in a few calls. POST /crm/v3/objects/products/batch/update accepts up to 100 records per request, each with the product ID and the new price value.
POST /crm/v3/objects/products/batch/update with 50 entries, each setting the price property to the new list value.
Product picker for a sales tool
Build a product picker inside a sales tool that searches the live HubSpot catalogue. POST /crm/v3/objects/products/search with a filter on SKU or name returns matching products with their price and custom properties so the rep selects the right SKU when building a quote.
POST a search to /crm/v3/objects/products/search filtering hs_sku CONTAINS_TOKEN 'AB-' and return the first 25 matching products.
AI agent execution through Jentic
An agent that needs to manage the catalogue discovers this API via Jentic's intent search using a query like 'create a hubspot product' or 'find hubspot product by sku', loads the input schema for the chosen operation, and executes the call with credentials supplied from your Jentic One instance. The same flow handles batch and search.
Search Jentic for 'create a hubspot product', load POST /crm/v3/objects/products/batch/create, and execute with one product entry.
Key Endpoints
11 endpoints — the hubspot crm products api manages the product catalogue inside a hubspot portal - the master list of products that quotes, deals, and orders reference through line items.
METHOD
PATH
DESCRIPTION
GET
/crm/v3/objects/products/{productId}
Read a single product by ID
PATCH
/crm/v3/objects/products/{productId}
Update properties on a product
DELETE
/crm/v3/objects/products/{productId}
Archive a product
GET
/crm/v3/objects/products
List products with pagination
POST
/crm/v3/objects/products/batch/create
Create up to 100 products in one call
POST
/crm/v3/objects/products/batch/update
Update up to 100 products in one call
POST
/crm/v3/objects/products/batch/read
Read up to 100 products by ID
POST
/crm/v3/objects/products/batch/archive
Archive up to 100 products in one call
GET
/crm/v3/objects/products/{productId}
Read a single product by ID
PATCH
/crm/v3/objects/products/{productId}
Update properties on a product
DELETE
/crm/v3/objects/products/{productId}
Archive a product
GET
/crm/v3/objects/products
List products with pagination
POST
/crm/v3/objects/products/batch/create
Create up to 100 products in one call
POST
/crm/v3/objects/products/batch/update
Update up to 100 products in one call
POST
/crm/v3/objects/products/batch/read
Read up to 100 products by ID
POST
/crm/v3/objects/products/batch/archive
Archive up to 100 products 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.
P
Products
- Foundational (D-)42/100
74
Foundational Compliance63
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience94
Agent Usability63
Security67
AI DiscoverabilityPowered 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.
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.
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).
67
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
67%
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 Products 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 catalogue property names it expects, and handling token refresh yourself. Through Jentic you install once, import Products from the API Directory, store the token once, and your agent calls it.
Permission scoping
This API works against the products object collection, with the product id in the URL path (/crm/v3/objects/products/{productId}) on reads, updates, and deletes. Limit the agent to the operations it needs, such as reading and searching products, so destructive paths like product 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 'create a HubSpot product' or 'find a product by SKU', and Jentic returns the matching Products operation with its input schema, including the property names the catalogue uses, 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 Products API through Jentic.
What authentication does the HubSpot Products API use?
It accepts OAuth 2.0 access tokens and private app access tokens passed as a Bearer credential in the Authorization header. Through Jentic, the token is stored encrypted in the credential vault and attached at request time.
Can I attach a product to a deal or quote through this API?
Not directly. Products are linked to deals and quotes via line items. Create the product here, then create a line item that references the product ID and associate the line item with the deal or quote.
What are the rate limits for the HubSpot Products API?
Standard HubSpot account limits apply, typically 100 requests per 10 seconds for OAuth apps. Use the batch endpoints under /crm/v3/objects/products/batch/* to ingest or update up to 100 products in a single request.
How do I find a product by SKU through Jentic?
Search Jentic with 'find hubspot product by sku', load POST /crm/v3/objects/products/search, and execute with a filterGroups payload setting propertyName=hs_sku and an EQ operator on the SKU value.
Is the HubSpot Products API free?
It is included with HubSpot accounts that have CRM access enabled; there is no per-call charge. The Commerce Hub adds related capabilities (quotes, payments) but the products endpoints themselves are part of the standard CRM.
How do I bulk-archive discontinued products?
POST /crm/v3/objects/products/batch/archive with an inputs array of up to 100 product IDs. Archived products no longer appear in the active list but can still be read by ID for historical reporting.
Can I limit what my agent is allowed to do with the HubSpot Products API?
Yes. Jentic One runs self-hosted, so your own rules decide which Products operations and credentials the agent may use. You can allow only the calls it needs, such as reading a product at /crm/v3/objects/products/{productId} and searching the catalogue, while excluding destructive paths like product delete or batch archive. Because your HubSpot token is held by your own instance and attached at request time, the agent can reach only the operations you have permitted.
GET STARTED