HubSpot CRM Deal Splits
Browse all Hubspot APIs✓ Official Vendor SpecCRMDeal Pipelineoauth2, apiKey2 EndpointsREST
For Agents
Read and upsert HubSpot deal-split records to attribute deal credit across multiple owners via batch endpoints on /crm/v3/objects/deals/splits.
Use for: I need to split a $100,000 deal 70/30 between the AE and the SE, Read the current split breakdown for a list of recently closed deals, Update the splits on a deal after the manager joined the opportunity late, Bulk-set splits for every deal closed in the last quarter from a commission file
Not supported: Does not calculate commission payouts, run payroll, or manage quota plans — use for setting credit-percentage splits on HubSpot deals only.
The HubSpot Deal Splits API attributes credit and revenue from a single deal across multiple HubSpot owners so commission and reporting can reflect collaborative selling. It exposes two batch endpoints — read and upsert — that operate on deal-split records keyed off the parent deal ID. This is the API to call when a deal closes and the rep, manager, or specialist all need percentage credit on the opportunity.
Install Jentic One Beta
Connect the CRM Deal Splits to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CRM Deal Splits, 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 CRM Deal Splits API.
Batch-read existing splits for a list of deals via POST /crm/v3/objects/deals/splits/batch/read
Set or update splits for multiple deals in one call with POST /crm/v3/objects/deals/splits/batch/upsert
Allocate fractional credit to each contributing owner on a closed deal
Reset splits when deal ownership changes mid-cycle by upserting new percentages
Reconcile commission reports by pulling all splits across a batch of deals
Use Cases
Patterns agents use CRM Deal Splits API for, with concrete tasks.
★ Commission Allocation on Closed Deals
When deals close, attribute the right percentage of credit to each contributing owner so commissions match the team's collaborative selling model. The batch upsert endpoint accepts a list of deals with their owner and percentage allocations in a single call, which keeps a quarterly commission run within rate limits. Splits are stored on the deal, so downstream reports pick up the allocation automatically.
Call POST /crm/v3/objects/deals/splits/batch/upsert with deal 12345 split 70 percent to owner 100 and 30 percent to owner 200, then verify the 200 response.
Mid-Cycle Owner Re-allocation
Re-allocate splits when a deal's team changes mid-pipeline — for example, when a Customer Success rep is added late in the cycle and needs partial credit. Upserting new splits replaces the prior allocation atomically for that deal, so reports never see partial states. Pair with a search to find affected deals first.
Upsert a new split for deal 67890 with 60 percent to AE owner 101, 30 percent to manager owner 102, and 10 percent to SE owner 103.
Quarterly Commission Reconciliation
Pull splits in bulk for every deal closed in the quarter to reconcile against the commission system. The batch read endpoint returns split records for up to 100 deals at a time, including each owner ID and percentage. Combine with a deal search filtered to closedwon to walk the full closed-deal set quickly.
Batch-read splits for the 100 deals closed last quarter via POST /crm/v3/objects/deals/splits/batch/read, then sum percentages per owner ID.
Agent-Driven Split Updates via Jentic
An AI agent reading commission rule changes from a spreadsheet updates HubSpot deal splits without an engineer wiring a new batch job. Through Jentic the agent searches for the upsert operation, loads the input schema, and executes it with the parsed allocations. The flow runs on a single Jentic credential without exposing the HubSpot key.
Use Jentic to search 'update HubSpot deal splits in batch', load the POST /crm/v3/objects/deals/splits/batch/upsert schema, and execute it with the parsed split rows.
Key Endpoints
2 endpoints — the hubspot deal splits api attributes credit and revenue from a single deal across multiple hubspot owners so commission and reporting can reflect collaborative selling.
METHOD
PATH
DESCRIPTION
POST
/crm/v3/objects/deals/splits/batch/read
Batch-read splits for a list of deals
POST
/crm/v3/objects/deals/splits/batch/upsert
Batch-set or update splits across multiple deals
POST
/crm/v3/objects/deals/splits/batch/read
Batch-read splits for a list of deals
POST
/crm/v3/objects/deals/splits/batch/upsert
Batch-set or update splits across multiple deals
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
HubSpot OAuth tokens and private app keys are stored encrypted in the Jentic vault. Agents receive a scoped execution token — the raw HubSpot credential is injected at call time and never enters the agent's context.
Intent-based discovery
Agents search Jentic by intent (e.g., 'split HubSpot deal credit across owners') and Jentic returns the batch upsert operation with its schema, so the agent calls the right endpoint without browsing HubSpot docs.
Time to first call
Direct HubSpot integration: 1-2 days for OAuth scopes and batch payload assembly. Through Jentic: under 1 hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using CRM Deal Splits API through Jentic.
What authentication does the HubSpot Deal Splits API use?
Deal Splits accepts OAuth 2.0 access tokens with the crm.objects.deals scope or HubSpot private app API keys passed in the private-app header. Through Jentic the token is held in the MAXsystem vault and injected at execution time so it never enters the agent's context.
Can I split a HubSpot deal across more than two owners?
Yes. The upsert payload accepts a list of owner-percentage pairs per deal, so you can allocate credit across three or more reps in one call. Percentages must sum to 100 for the deal.
What are the rate limits for the HubSpot Deal Splits API?
Splits share HubSpot's account-wide limit — typically 100 requests per 10 seconds for OAuth apps and 190 per 10 seconds for private apps on paid tiers. Each batch call counts as one request, so use the batch endpoints for any commission run touching more than a handful of deals.
How do I update splits on a deal through Jentic?
Run jentic.search('upsert HubSpot deal splits'), load the schema for POST /crm/v3/objects/deals/splits/batch/upsert, and execute it with the deal IDs and owner-percentage list. Jentic returns the upsert result as structured JSON for the next step in your workflow.
Is there a single-record endpoint for one deal's splits?
No. Both endpoints are batch-only. To work with a single deal, send a batch request with one entry — HubSpot returns the same shape and the call counts as one request against your rate limit.
Are deal splits available on every HubSpot tier?
Deal splits are a paid-tier feature in HubSpot Sales Hub. The API will return an authorization error on free or starter accounts that do not have the feature enabled. Confirm the tier before wiring up a commission integration.
GET STARTED