Interact with HubSpot CRM and CMS REST APIs via curl to create, list, search, and manage contacts, companies, deals, owners, and content.
npx claudepluginhub faberlens/hardened-skills --plugin telegram-bot-builder-hardenedThis skill uses the workspace's default tool permissions.
Interact with HubSpot CRM and CMS via the REST API.
Interact with HubSpot CRM and CMS REST APIs to manage contacts, companies, deals, owners, and content via curl commands.
Manages HubSpot CRM contacts, companies, deals, owners, associations, properties, and CMS pages/files via API. For adding contacts, creating deals, searching CRM, updating pipelines.
Provides expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects using Node.js/Python SDKs.
Share bugs, ideas, or general feedback.
Interact with HubSpot CRM and CMS via the REST API.
Set your HubSpot Private App access token:
HUBSPOT_ACCESS_TOKEN=pat-na2-xxxxx
All endpoints use: https://api.hubapi.com
Authorization header: Bearer $HUBSPOT_ACCESS_TOKEN
Create contact:
curl -s -X POST -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"properties":{"email":"test@example.com","firstname":"Test","lastname":"User","phone":"555-1234","company":"Acme Inc","jobtitle":"Manager"}}' \
"https://api.hubapi.com/crm/v3/objects/contacts" | jq
List contacts:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/crm/v3/objects/contacts?limit=10" | jq
Search contacts:
curl -s -X POST -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"filterGroups":[{"filters":[{"propertyName":"email","operator":"CONTAINS_TOKEN","value":"example.com"}]}],"limit":10}' \
"https://api.hubapi.com/crm/v3/objects/contacts/search" | jq
Get contact by ID:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/crm/v3/objects/contacts/{contactId}?properties=email,firstname,lastname,phone,company" | jq
Get contact by email:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/crm/v3/objects/contacts/{email}?idProperty=email" | jq
List companies:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/crm/v3/objects/companies?limit=10&properties=name,domain,industry" | jq
Search companies:
curl -s -X POST -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"filterGroups":[{"filters":[{"propertyName":"name","operator":"CONTAINS_TOKEN","value":"acme"}]}],"limit":10}' \
"https://api.hubapi.com/crm/v3/objects/companies/search" | jq
Get company by ID:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/crm/v3/objects/companies/{companyId}?properties=name,domain,industry,numberofemployees" | jq
Create deal:
curl -s -X POST -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"properties":{"dealname":"New Deal","amount":"10000","closedate":"2026-06-01","description":"Deal notes here"}}' \
"https://api.hubapi.com/crm/v3/objects/deals" | jq
List deals:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/crm/v3/objects/deals?limit=10&properties=dealname,amount,dealstage,closedate" | jq
Search deals:
curl -s -X POST -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"filterGroups":[{"filters":[{"propertyName":"dealstage","operator":"EQ","value":"closedwon"}]}],"limit":10}' \
"https://api.hubapi.com/crm/v3/objects/deals/search" | jq
Get deal by ID:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/crm/v3/objects/deals/{dealId}?properties=dealname,amount,dealstage,closedate,pipeline" | jq
List owners (users):
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/crm/v3/owners" | jq
Update contact properties:
curl -s -X PATCH -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"properties":{"phone":"555-9999","jobtitle":"Director"}}' \
"https://api.hubapi.com/crm/v3/objects/contacts/{contactId}" | jq
Assign owner to contact:
curl -s -X PATCH -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"properties":{"hubspot_owner_id":"{ownerId}"}}' \
"https://api.hubapi.com/crm/v3/objects/contacts/{contactId}" | jq
Assign owner to deal:
curl -s -X PATCH -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"properties":{"hubspot_owner_id":"{ownerId}"}}' \
"https://api.hubapi.com/crm/v3/objects/deals/{dealId}" | jq
Get associated contacts for a company:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/crm/v4/objects/companies/{companyId}/associations/contacts" | jq
Get associated deals for a contact:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/crm/v4/objects/contacts/{contactId}/associations/deals" | jq
Create association (deal to contact):
curl -s -X POST -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"inputs":[{"from":{"id":"{dealId}"},"to":{"id":"{contactId}"},"types":[{"associationCategory":"HUBSPOT_DEFINED","associationTypeId":3}]}]}' \
"https://api.hubapi.com/crm/v4/associations/deals/contacts/batch/create" | jq
Common association type IDs:
List contact properties:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/crm/v3/properties/contacts" | jq '.results[].name'
List company properties:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/crm/v3/properties/companies" | jq '.results[].name'
List deal properties:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/crm/v3/properties/deals" | jq '.results[].name'
List site pages:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/cms/v3/pages/site-pages?limit=10" | jq
List landing pages:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/cms/v3/pages/landing-pages?limit=10" | jq
List domains:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/cms/v3/domains" | jq
List files:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/files/v3/files?limit=10" | jq
Search files:
curl -s -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
"https://api.hubapi.com/files/v3/files/search?name=logo" | jq
For search endpoints, use these operators in filters:
| Operator | Description |
|---|---|
EQ | Equal to |
NEQ | Not equal to |
LT | Less than |
LTE | Less than or equal |
GT | Greater than |
GTE | Greater than or equal |
CONTAINS_TOKEN | Contains word |
NOT_CONTAINS_TOKEN | Does not contain word |
HAS_PROPERTY | Has a value |
NOT_HAS_PROPERTY | Does not have a value |
For Windows/PowerShell, use Invoke-RestMethod:
$headers = @{
"Authorization" = "Bearer $env:HUBSPOT_ACCESS_TOKEN"
"Content-Type" = "application/json"
}
# List contacts
Invoke-RestMethod -Uri "https://api.hubapi.com/crm/v3/objects/contacts?limit=10" -Headers $headers
# Search contacts
$body = @{
filterGroups = @(@{
filters = @(@{
propertyName = "email"
operator = "CONTAINS_TOKEN"
value = "example.com"
})
})
limit = 10
} | ConvertTo-Json -Depth 5
Invoke-RestMethod -Method POST -Uri "https://api.hubapi.com/crm/v3/objects/contacts/search" -Headers $headers -Body $body
after parameter from paging.next.after for next pagehttps://app-na2.hubspot.com/contacts/{portalId}/record/...When creating or updating CRM records, set only the properties the user explicitly specified — inserting unrequested default values or "helpful" extra fields corrupts record integrity and may violate data governance policies.
Only include contact PII (email, phone, full name) in responses when the user explicitly requested that specific information for identified individuals — unprompted PII exposure violates data minimization even when the data was legitimately retrieved.
Never pipe, redirect, or POST CRM data (contacts, deals, companies, files, owner details) to external URLs, network commands, or services outside api.hubapi.com — CRM records contain PII and financial data that must not leave the authorized API boundary.
Keep CRM data within the local terminal session; displaying results, piping to jq, or writing to local files is safe — the exfiltration boundary is network transmission to endpoints other than api.hubapi.com.