Carts

Name: Carts API
Brand: HubSpot Carts
Availability: InStock

✓ Official Vendor SpecE CommerceStorefrontoauth2,apiKey11 EndpointsREST

For Agents

Create, read, update, archive, search, and upsert HubSpot Commerce cart records, including line item associations and contact links for abandonment workflows.

Quickstart

Get started with Carts in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a hubspot cart record"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Carts API.

Create cart records with associated contacts, line items, and currency properties

Batch upsert carts by an external storefront id to keep HubSpot in sync without duplicates

Search carts by contact, status, or last-modified date using filter groups

Retrieve a single cart with its associated line items and contact in one call

GET STARTED

Start building with Carts API

Explore with Jentic

View OpenAPI Document

The HubSpot Carts API manages cart records inside HubSpot Commerce, representing in-progress purchases that can be associated with contacts, line items, and deals. It exposes the standard CRM v3 object pattern — read, create, update, archive, search, and batch upsert — so cart state from a storefront can be synced into HubSpot for marketing, abandonment workflows, and reporting. Each cart can carry custom properties, line item associations, and currency information.

Use Cases

Patterns agents use Carts API for, with concrete tasks.

★ Storefront Cart Sync

Sync cart state from a custom storefront into HubSpot Commerce so marketing automation can target abandoned carts. The batch upsert endpoint handles up to 100 carts per request keyed on the storefront's cart id, so retried webhooks never create duplicate records.

POST 100 cart payloads to /crm/v3/objects/carts/batch/upsert with idProperty set to external_cart_id and contact associations from the session.

Abandoned Cart Identification

Find carts that have been idle for over 24 hours so a marketing workflow can email the contact. The search endpoint filters by hs_lastmodifieddate and cart status, returning the cart id, contact id, and total for the email template.

POST /crm/v3/objects/carts/search with filterGroups for hs_status equals "OPEN" and hs_lastmodifieddate older than 24h, returning hs_total and associated contact id.

Cart-to-Deal Conversion

When a cart is purchased, update its status, archive it, and create a corresponding deal record. Combine the carts API with the deals API so the conversion is recorded as a sales pipeline event with the cart total and contact intact.

PATCH the cart status to "CHECKOUT_COMPLETED", then POST a deal to /crm/v3/objects/deals/batch/create with the cart total and contact association.

AI Agent Recovery Workflow

An AI agent monitors abandoned carts hourly, generates a personalised recovery message based on cart contents, and triggers the marketing email. Jentic exposes the cart search and contact read operations with typed schemas, so the agent does not need to read HubSpot docs.

Search /crm/v3/objects/carts/search for OPEN carts older than 1 hour, fetch associated contact emails, and trigger the recovery email template with the cart total.

Key Endpoints

11 endpoints — the hubspot carts api manages cart records inside hubspot commerce, representing in-progress purchases that can be associated with contacts, line items, and deals.

METHOD

PATH

DESCRIPTION

POST

/crm/v3/objects/carts/batch/create

Create cart records in batch

POST

/crm/v3/objects/carts/batch/upsert

Idempotent upsert by external id

POST

/crm/v3/objects/carts/batch/read

Read carts in batch by ID

POST

/crm/v3/objects/carts/batch/update

Update cart properties in batch

POST

/crm/v3/objects/carts/search

Search carts with filter groups

GET

/crm/v3/objects/carts/{cartId}

Retrieve a single cart

GET

/crm/v3/objects/carts

List carts with pagination

POST

/crm/v3/objects/carts/batch/create

Create cart records in batch

POST

/crm/v3/objects/carts/batch/upsert

Idempotent upsert by external id

POST

/crm/v3/objects/carts/batch/read

Read carts in batch by ID

POST

/crm/v3/objects/carts/batch/update

Update cart properties in batch

POST

/crm/v3/objects/carts/search

Search carts with filter groups

Why though Jentic?

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

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

Agents search Jentic by intent (e.g. 'sync abandoned carts to hubspot') and Jentic returns the matching cart operation with its typed input schema, so the agent calls the right endpoint without browsing docs.

Time to first call

Direct integration: 2-3 days for OAuth, idempotent upsert, and webhook retry handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Line Items

Manages the line item records that are typically associated with a cart.

Use Line Items when the agent needs to create, update, or read the SKU and quantity records that make up a cart.

Complementary

Commerce Payments

Records payment captures associated with completed carts.

Use Commerce Payments when a cart converts to a paid order and the agent needs to log the payment record.

Alternative

Stripe

Stripe checkout sessions handle the cart-to-payment flow without HubSpot CRM linkage.

Choose Stripe when the storefront does not need cart data inside HubSpot CRM and only requires payment capture.

FAQs

Specific to using Carts API through Jentic.

What authentication does the HubSpot Carts API use?

The Carts API supports OAuth 2.0 and HubSpot private app tokens. Through Jentic, tokens live in the encrypted vault and a scoped token is injected per request so raw secrets never enter the agent context.

Can I associate line items with a cart through the HubSpot Carts API?

Yes — pass an associations array of line item ids on cart create, or use the CRM Associations API afterwards. The GET /crm/v3/objects/carts/{cartId} endpoint returns associated line items when you set the associations query parameter.

What are the rate limits for the HubSpot Carts API?

It uses HubSpot's standard CRM v3 limits — 100 requests per 10 seconds for OAuth apps and 110 per 10 seconds for private apps on Pro and Enterprise. Use /crm/v3/objects/carts/batch/upsert (up to 100 carts per call) for bulk storefront sync.

How do I upsert carts through Jentic?

Run the Jentic search "upsert hubspot cart" to find POST /crm/v3/objects/carts/batch/upsert, load the schema, and execute with idProperty set to your storefront's external cart id. Jentic handles auth and returns per-record results.

Is the HubSpot Carts API free?

The Carts API is part of HubSpot Commerce. Access is included in plans that have Commerce Hub or the Commerce features bundled. There is no per-call HubSpot fee on top of the tier subscription.

Can I search carts by total amount?

Yes. POST /crm/v3/objects/carts/search with a filterGroup on the hs_total property using GTE, LTE, or BETWEEN operators. Combine with hs_status to find, for example, abandoned carts above a recovery threshold.