HubSpot Payments
Browse all Hubspot APIs✓ Official Vendor SpecCRMContact Managementoauth2,apiKey4 EndpointsREST
For Agents
Read, list, batch-read, and search HubSpot CRM payment records to reconcile transactions and surface payment history alongside other CRM objects.
Use for: I need to find all payments above a given amount, Get the payment record for a specific payment ID, List payments created in the last 7 days, Search payments by their status property
Not supported: Does not capture, refund, or void payments — use for reading existing HubSpot CRM payment records only.
The HubSpot CRM Payments API exposes payment records as a CRM object so agents can read, list, batch-read, and search the payments stored against a HubSpot portal. Each payment record represents a financial transaction associated with a contact, deal, or order in the CRM and includes properties such as gross amount, currency, status, and creation date. The API is read-only — payment records themselves are produced by HubSpot's commerce flows or by the Commerce Payments API rather than created here. Use it for reporting on settled payments, reconciling CRM data with an upstream commerce system, and exposing payment history to sales workflows.
Install Jentic One Beta
Connect the Payments to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Payments, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 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.
Capabilities
What an agent can do with Payments API.
Read a single payment record by ID with property selection
List payment records with cursor-based pagination
Read up to 100 payment records in one batch call by ID
Search payments by property filters such as status, amount, or create date
Retrieve a payment with associations to its contact, deal, or order
Page through payments sorted by createdate or any other property
Use Cases
Patterns agents use Payments API for, with concrete tasks.
★ Payment reconciliation report
Pull all payment records from the last reporting period and reconcile them against the upstream commerce or accounting system. Use POST /crm/v3/objects/payments/search with a createdate filter and pagination to retrieve every payment, then match each against the equivalent record in the source of truth.
POST a search to /crm/v3/objects/payments/search filtering createdate greater than the last reporting cutoff, sorted ascending, and page until paging.next is empty.
Payment lookup for sales context
Surface a customer's payment history inside a sales tool. GET /crm/v3/objects/payments/{paymentsId} returns a payment record with its properties, and a batch read pulls the recent payments for a list of customers. Lets a sales rep see settled payments before a renewal call without leaving the workflow.
GET /crm/v3/objects/payments/{paymentsId} for a known payment ID and return the gross amount and status fields.
Status-filtered payment monitoring
Monitor failed or refunded payments by searching the payments object for non-success statuses. Useful for triggering recovery workflows or escalating disputed charges to the finance team.
POST a search to /crm/v3/objects/payments/search filtering on a status property equal to FAILED, sorted by createdate descending, and return the first 25 records.
AI agent execution through Jentic
An agent that needs to query payment records discovers this API via Jentic's intent search using a query like 'list hubspot payments', loads the input schema for the chosen operation, and executes the call with credentials supplied from the Jentic vault. The same flow handles batch read and filtered search.
Search Jentic for 'list hubspot payments', load GET /crm/v3/objects/payments, and execute it with limit=20.
Key Endpoints
4 endpoints — the hubspot crm payments api exposes payment records as a crm object so agents can read, list, batch-read, and search the payments stored against a hubspot portal.
METHOD
PATH
DESCRIPTION
GET
/crm/v3/objects/payments
List payment records with pagination
GET
/crm/v3/objects/payments/{paymentsId}
Read a single payment record by ID
POST
/crm/v3/objects/payments/batch/read
Read up to 100 payment records by ID
POST
/crm/v3/objects/payments/search
Search payment records with filter groups and sorts
GET
/crm/v3/objects/payments
List payment records with pagination
GET
/crm/v3/objects/payments/{paymentsId}
Read a single payment record by ID
POST
/crm/v3/objects/payments/batch/read
Read up to 100 payment records by ID
POST
/crm/v3/objects/payments/search
Search payment records with filter groups and sorts
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
HubSpot OAuth and private app tokens live encrypted in the Jentic vault. Jentic attaches the Authorization header at execution time, so the token never enters the agent's prompt context, transcript, or logs.
Intent-based discovery
Agents search by intent (e.g. 'list hubspot payments' or 'search payments by amount') and Jentic returns the matching Payments operation with its JSON Schema for direct execution.
Time to first call
Direct integration: 2-4 hours for OAuth, pagination, and search filter wiring. Through Jentic: under 20 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe API
Full payment platform that processes charges and exposes settled payment data
Choose Stripe when payments are processed outside HubSpot and you want the source-of-truth view.
FAQs
Specific to using Payments API through Jentic.
What authentication does the HubSpot Payments 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 create or refund payments through this API?
No. The CRM Payments API is read-only — it exposes only read, list, batch read, and search. Payment creation, capture, and refund flows are handled by HubSpot's Commerce Payments product and its dedicated API.
What are the rate limits for the HubSpot Payments API?
It shares HubSpot's account-level rate limits, typically 100 requests per 10 seconds for OAuth apps. Use POST /crm/v3/objects/payments/batch/read to fetch up to 100 records in a single request and stay within limits.
How do I search for payments above a given amount through Jentic?
Search Jentic with 'search hubspot payments by amount', load POST /crm/v3/objects/payments/search, and execute with a filterGroups array specifying the amount property, the GT operator, and the threshold value.
Is the HubSpot Payments API free?
It is included on accounts that have HubSpot Commerce Hub or the relevant payments add-on enabled. The endpoints themselves do not carry per-call pricing; they share account-level API rate limits.
How do I find the deal or contact a payment is linked to?
GET /crm/v3/objects/payments/{paymentsId} with the associations query parameter set to deals or contacts; the response includes the linked record IDs in the associations object.
GET STARTED