Subscriptions

Name: Subscriptions API
Brand: HubSpot Subscriptions
Availability: InStock

✓ Official Vendor SpecPaymentsBilling Subscriptionsoauth2,apiKey11 EndpointsREST

For Agents

Create, read, update, archive, search, and upsert HubSpot Commerce subscription records, with batch endpoints for syncing recurring billing state from an external billing system.

Quickstart

Get started with Subscriptions 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 subscription record"

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

Capabilities

What an agent can do with Subscriptions API.

Create subscription records with billing cycle, next renewal date, and status properties

Batch upsert subscriptions by an external billing id to keep HubSpot in sync without duplicates

Search subscriptions by status, contact, or renewal date using filter groups

Retrieve a subscription with its associated contacts, deal, and line items in one call

GET STARTED

Start building with Subscriptions API

Explore with Jentic

View OpenAPI Document

The HubSpot Commerce Subscriptions API manages subscription records inside HubSpot Commerce — the CRM-side representation of a recurring billing relationship between a contact and a product. It exposes the standard CRM v3 object pattern with batch read, create, update, archive, search, and upsert against the subscriptions object. Each subscription can carry properties such as billing cycle, next renewal date, status, and associated contact, deal, and line items, mirroring an external billing system into the CRM.

Use Cases

Patterns agents use Subscriptions API for, with concrete tasks.

★ Billing System Mirror

Mirror subscription state from an external billing platform into HubSpot so sales and customer success can see active and at-risk subscriptions in the CRM. The batch upsert endpoint handles up to 100 subscriptions per request keyed on the billing system's subscription id, eliminating duplicates from retried webhooks.

POST 100 subscription payloads to /crm/v3/objects/subscriptions/batch/upsert with idProperty = external_subscription_id and hs_status from the billing source.

Renewal Pipeline

Search for subscriptions renewing in the next two weeks so customer success can run a renewal play. The search endpoint filters by hs_next_renewal_date and status, returning the subscription id, contact id, and amount for the renewal queue.

POST /crm/v3/objects/subscriptions/search with filterGroups for hs_status = ACTIVE and hs_next_renewal_date in the next 14 days, returning hs_amount and contact id.

Churn Analysis

Search for subscriptions cancelled in the last quarter, group by cancellation reason, and feed into a churn dashboard. The CRM-side record keeps cancellation context alongside contact properties for cohort analysis.

Search /crm/v3/objects/subscriptions/search with filterGroups for hs_status = CANCELLED and hs_cancelled_date in the last 90 days, returning hs_cancellation_reason and contact id.

AI Agent Renewal Outreach

An AI agent runs daily to identify upcoming renewals, drafts a personalised outreach message, and assigns a task to the account owner. Jentic exposes the search and contact read operations with typed schemas, so the agent does not need to read HubSpot docs.

Search subscriptions renewing in the next 14 days, fetch the contact owner, and create a task for each owner via the HubSpot tasks API with the renewal context.

Key Endpoints

11 endpoints — the hubspot commerce subscriptions api manages subscription records inside hubspot commerce — the crm-side representation of a recurring billing relationship between a contact and a product.

METHOD

PATH

DESCRIPTION

POST

/crm/v3/objects/subscriptions/batch/create

Create subscription records in batch

POST

/crm/v3/objects/subscriptions/batch/upsert

Idempotent upsert by external id

POST

/crm/v3/objects/subscriptions/batch/read

Read subscriptions in batch by ID

POST

/crm/v3/objects/subscriptions/batch/update

Update subscription properties in batch

POST

/crm/v3/objects/subscriptions/search

Search subscriptions by filter groups

GET

/crm/v3/objects/subscriptions/{subscriptionId}

Retrieve a single subscription

GET

/crm/v3/objects/subscriptions

List subscriptions with pagination

POST

/crm/v3/objects/subscriptions/batch/create

Create subscription records in batch

POST

/crm/v3/objects/subscriptions/batch/upsert

Idempotent upsert by external id

POST

/crm/v3/objects/subscriptions/batch/read

Read subscriptions in batch by ID

POST

/crm/v3/objects/subscriptions/batch/update

Update subscription properties in batch

POST

/crm/v3/objects/subscriptions/search

Search subscriptions by 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 appear in agent prompts or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'sync subscriptions to hubspot') and Jentic returns the matching subscriptions operation with its typed input schema, so the agent calls the right endpoint without doc lookup.

Time to first call

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

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Commerce Payments

Records the payments captured against an active subscription.

Use Commerce Payments when the agent needs to log the individual payment events that a subscription generates over time.

Complementary

Invoices

Tracks invoice records issued to subscribers.

Use Invoices when the agent needs to mark a subscription invoice as paid or generate an invoice for a renewal.

Alternative

Stripe

Stripe Billing manages real subscription state and billing — HubSpot subscriptions are the CRM-side mirror.

Choose Stripe when the agent must change billing state (cancel, pause, change price); use HubSpot Subscriptions to mirror those changes into CRM.

FAQs

Specific to using Subscriptions API through Jentic.

What authentication does the HubSpot Subscriptions API use?

It supports OAuth 2.0 and HubSpot private app tokens. Through Jentic, tokens are stored encrypted in the vault and a scoped token is injected per request, keeping raw credentials out of the agent context.

Can I cancel a subscription via the HubSpot Subscriptions API?

You can update the CRM record (set hs_status to CANCELLED via PATCH /crm/v3/objects/subscriptions/{subscriptionId}) but the API does not cancel billing at an external processor. Cancel at the billing system first, then update the HubSpot record to reflect that state.

What are the rate limits for the HubSpot Subscriptions API?

Standard CRM v3 limits apply — 100 requests per 10 seconds for OAuth apps and 110 per 10 seconds for private apps. Use /crm/v3/objects/subscriptions/batch/upsert (up to 100 records per call) when syncing from a billing system.

How do I upsert subscriptions through Jentic?

Run the Jentic search "upsert hubspot subscription" to find POST /crm/v3/objects/subscriptions/batch/upsert, load the schema, and execute with idProperty set to your billing system's subscription id. Jentic handles authentication.

Is the HubSpot Subscriptions API free?

Access requires HubSpot Commerce Hub. There is no per-call HubSpot fee on top of the Commerce subscription, but the underlying tier price applies.

Can I associate a subscription with a deal and a contact?

Yes — pass an associations array on create, or use the CRM Associations API afterwards, to link a single subscription to a deal, contact, and line items. The single-record GET supports an associations parameter to return linked IDs in one call.