The HubSpot Commerce Payments API exposes payment records inside HubSpot Commerce, representing captured payments that can be associated with contacts, deals, and invoices. It follows the standard CRM v3 object pattern with batch read, create, update, archive, search, and upsert operations against the commerce_payments object. Records carry properties such as amount, currency, payment method, processor, and reference id, providing a CRM-side ledger that mirrors the payments captured by your processor.
11 endpointsThe 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.
11 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.