Hubspot APIs
93 APIs957 Endpoints12 Categories
Categories
API Catalog(45 of 93)
Appointments
The HubSpot Appointments API exposes the appointment object inside HubSpot CRM as a generic object resource. It supports listing, creating, updating, archiving, batch operations, and search across appointment records, mirroring the standard HubSpot CRM object shape with custom property maps. Use this API to read or mutate appointment objects programmatically alongside contacts, deals, and other CRM resources.
11 endpointsBucket_Test111
The HubSpot Bucket_Test111 API exposes a custom CRM object type used internally by HubSpot for bucket-style record collections. It provides full CRUD plus search and batch operations against the bucket_test111s object set within the standard CRM v3 object model. Records can be created, archived, merged with other CRM data, and queried alongside contacts, companies, and deals using the same association graph.
10 endpointsBusiness Units
The HubSpot Business Units API exposes a single endpoint for retrieving the Business Unit records associated with a HubSpot user. Business Units allow multi-brand HubSpot accounts to segment marketing assets, forms, and tracking under separate logos and identities. This API is read-only and is typically used by agents or integrations that need to surface the correct brand context for a given user before performing a downstream action.
1 endpointsCalls
The HubSpot Calls API manages call engagement records in the CRM — the structured log of inbound and outbound calls associated with contacts, companies, and deals. It exposes batch CRUD plus search and upsert against the calls object using the standard CRM v3 object pattern. Each call record can carry properties such as duration, call direction, recording URL, notes, and outcome, and can be associated with other CRM objects.
11 endpointsCommunications
The HubSpot CRM Communications API manages communication engagement records — log entries representing channel-specific messages such as WhatsApp, LinkedIn, or SMS conversations associated with contacts and companies. It exposes the standard CRM v3 object pattern with batch read, create, update, archive, search, and upsert against the communications object. Records carry channel type, body, direction, and timestamp, providing a unified CRM activity timeline for non-email, non-call channels.
11 endpointsCompanies
The HubSpot Companies API manages company records — the primary CRM object representing organisations that a HubSpot user does business with. It exposes the standard CRM v3 object pattern with batch read, create, update, archive, search, upsert, and merge operations against the companies object. Each company record carries default properties such as name and domain, supports custom properties, and can be associated with contacts, deals, tickets, and other CRM objects.
12 endpointsContacts
The HubSpot Contacts API manages contact records — the primary CRM object representing the people a HubSpot user does business with. It exposes the standard CRM v3 object pattern with batch read, create, update, archive, merge, and a GDPR-compliant delete endpoint against the contacts object. Each contact carries default properties such as firstname, lastname, and email, supports custom properties, and can be associated with companies, deals, and tickets.
9 endpointsCourses
The HubSpot Courses API exposes the Courses CRM object so AI agents can read, create, update, archive, and search course records that sit alongside companies, contacts, and deals. It supports single-record and batch operations through the standard /crm/v3/objects/{objectType} surface, with full support for custom properties and pagination. Courses are commonly used by education, training, and onboarding teams that want learner enrollments tracked inside the same CRM as sales pipeline data.
11 endpointsCRM Associations
The HubSpot CRM Associations v4 API manages links between CRM objects — for example connecting a contact to a deal, a deal to a company, or any object pair allowed by the portal's association schema. It supports single and batch create, read, archive, and label operations, plus default association shortcuts and a high-usage report endpoint. This is the right surface for any workflow that mutates or reads relationships between standard or custom CRM objects.
10 endpointsCRM Associations Schema
The HubSpot CRM Associations Schema v4 API defines and reads the catalog of association types and labels available between CRM object pairs. It supports listing all configured association definitions, reading those for a specific object type pair, and creating, updating, or removing labels and configurations in batch. Use this API to set up the relationship vocabulary that the Associations API then operates on.
9 endpointsCRM Contracts
The HubSpot CRM Contracts API exposes a generic CRM object endpoint set parameterised by objectType, providing batch read, create, update, archive, search, and upsert operations against any CRM object collection — including standard objects like companies, contacts, deals, line items, products, tickets, and quotes. Each request takes the objectType as a path parameter and operates on the corresponding object collection using the same v3 patterns. It is the most general-purpose CRM v3 endpoint surface in the HubSpot API.
11 endpointsCRM Crm Owners
The HubSpot CRM Owners API returns the owners that can be assigned to CRM records (contacts, deals, companies, tickets, and custom objects) via the hubspot_owner_id property. It exposes a list endpoint and a single-owner lookup endpoint, both of which include team membership information when teams are enabled on the account. Agents typically call this API to resolve an owner email or ID before creating or updating a record so the new object lands with the correct sales rep or CSM.
2 endpointsCRM Deal Splits
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.
2 endpointsCRM Exports
The HubSpot CRM Exports API kicks off asynchronous bulk exports of CRM data — contacts, companies, deals, tickets, custom objects, or saved views — and returns the resulting file as XLSX or CSV. It exposes one endpoint to start an export task and a second to poll its status, which is the right pattern for pulling tens or hundreds of thousands of records without paginating the search API. Exports respect HubSpot property selection and filter criteria, so agents can specify exactly which columns and which records to include.
2 endpointsCRM Imports
The HubSpot CRM Imports API lets you bulk-load CRM records from CSV or spreadsheet files into HubSpot, mapping columns to standard or custom properties on contacts, companies, deals, and other objects. You can start a new import, monitor active imports, cancel an in-progress import, and inspect row-level errors after the job runs. It is the right tool for migrating data from another CRM, syncing periodic exports from external systems, or seeding a HubSpot account with historical records.
5 endpointsCRM Limits Tracking
The HubSpot CRM Limits Tracking API exposes the per-account quota information for the structural pieces of a HubSpot CRM portal — record counts, custom object types, custom properties, calculated properties, pipelines, and association labels. Each endpoint returns a current count, a maximum, and the remaining headroom so an integration or agent can check whether a planned action will exceed the account's plan limits before attempting it. It is the right tool for portal health checks, onboarding readiness validation, and pre-flight checks ahead of bulk imports or schema changes.
9 endpointsCRM Object Library
The HubSpot CRM Object Library API reports which CRM object types are enabled in a given HubSpot portal. It returns the enablement status for every object available in the library, including standard objects (contacts, companies, deals) and HubSpot-shipped specialised objects such as appointments, courses, and listings. Use it as a discovery step before integrating with a portal so the integration knows which objects it can write to and which require enablement first.
2 endpointsCRM Objects
The HubSpot CRM Objects API provides a unified interface for reading, creating, updating, and archiving any standard or custom CRM record by object type. It exposes generic endpoints that operate against companies, contacts, deals, line items, products, tickets, quotes, and any custom object you define on the portal. Batch read, create, update, and archive operations let agents move large volumes of records in a single call, and a search endpoint supports filtering and pagination across object types. Use it as the primary CRUD layer when you need a single integration that works across HubSpot's full object model rather than a separate client for each record type.
11 endpointsCRM Pipelines
The HubSpot CRM Pipelines API manages the pipelines and pipeline stages that define how records move through a workflow — sales deals through sales stages, support tickets through resolution stages, and any custom-object pipeline a portal defines. Endpoints cover full CRUD on pipelines and stages, plus dedicated audit endpoints that return the change history for both. Agents can list, read, create, update, and delete pipelines for a given object type, manage the ordered list of stages within each pipeline, and inspect every change made to either through the audit log. Use it to provision pipelines for a new portal, programmatically rename stages without breaking automation, or build governance dashboards from the audit history.
14 endpointsCRM Property Validations
The HubSpot CRM Property Validations API reads the validation rules HubSpot enforces on the properties of a CRM object — pattern checks, length constraints, enumerated value lists, and other input rules. It exposes a single object-type-level endpoint that returns every validation rule for the object's properties, plus a property-level endpoint that returns the rule for one named property. Use it to mirror HubSpot's validation logic in an external form, prevent failed writes by validating input client-side before calling the CRM Objects API, and document the input contract for downstream agents.
2 endpointsDeals
The HubSpot Deals API manages the deal records that drive HubSpot sales pipelines, exposing single and batch CRUD plus search across the standard /crm/v3/objects/deals surface. It supports pipeline stage transitions, deal property updates, deal merging, and association lookups so agents can move opportunities through pipelines programmatically. This is the primary API for any AI agent that needs to read, update, or report on revenue-stage data inside HubSpot.
12 endpointsDiscounts
The HubSpot Discounts API manages discount records that can be applied to HubSpot quotes and line items, exposing single and batch CRUD plus search across /crm/v3/objects/discounts. It supports percentage and fixed-amount discounts, custom properties, and standard pagination so agents can read, create, and reconcile discount catalogues programmatically. Use it whenever quote pricing depends on reusable discount records rather than ad-hoc line-item adjustments.
11 endpointsEmails
The HubSpot Emails CRM API manages email engagement records — logged emails, replies, and email metadata — that appear on contact and deal timelines. It exposes single and batch CRUD plus search across /crm/v3/objects/emails, supporting custom properties, pagination, and association lookups. Use it to log outbound emails sent from external tools, sync inbox replies, or pull engagement history for reporting; it does not send marketing or transactional emails.
11 endpointsFeedback Submissions
The HubSpot Feedback Submissions API exposes feedback submission records — typically NPS, CSAT, and CES survey responses captured by HubSpot's feedback tool — as a CRM object so AI agents can read and search them alongside contacts and deals. It exposes a list endpoint, a single-record retrieve, a batch read, and a search endpoint, all read-oriented because feedback submissions are created by HubSpot when a survey response arrives. Use it to pipe customer sentiment into reporting, route detractors, or correlate scores with deal outcomes.
4 endpointsFees
The HubSpot Fees API manages fee records used on quotes and line items, exposing single and batch CRUD plus search across /crm/v3/objects/fees. Fees represent shipping, handling, processing, or service charges that are added to a customer-facing quote alongside the product line items. Agents use this API to maintain a reusable fee catalogue, attach fees to quotes, and reconcile billed fees in commission or revenue reporting.
11 endpointsGoal Targets
The HubSpot Goal Targets API manages goal target records — the per-rep, per-team, or per-period targets that drive HubSpot's goals reporting (revenue goals, activity goals, deal-count goals). It exposes single and batch CRUD plus search across /crm/v3/objects/goal_targets, with custom property support so agents can program quota cycles, adjust targets mid-period, and reconcile actuals against plan. Use it to automate quarterly target rollouts, mid-cycle adjustments, and goal reporting pulls.
11 endpointsHubSpot CRM Custom Objects
Jentic publishes the only available OpenAPI specification for HubSpot CRM Custom Objects, keeping it validated and agent-ready. Define and operate on bespoke CRM object types that extend HubSpot beyond standard contacts, companies, deals, and tickets. Store industry-specific records — such as vehicles, properties, or subscriptions — with full association, search, batch, and merge support across the HubSpot CRM graph. Requires an Enterprise-tier HubSpot account.
15 endpointsHubSpot CRM Schemas
The HubSpot CRM Schemas API defines how custom objects store and represent information in the HubSpot CRM. A schema describes an object type's properties, primary display property, secondary display properties, searchable properties, required fields, and supported associations to other CRM objects. The API exposes operations to list all schemas, create a new schema for a custom object, fetch or update an existing schema by objectType, delete a schema, and add or remove associations between schemas — making it the foundation for any HubSpot integration that goes beyond the standard contact, company, deal, ticket, and quote objects.
7 endpointsInvoices
The HubSpot CRM Invoices API exposes the invoice object that sits alongside deals, line items, and quotes in HubSpot Commerce. Agents and integrations can create, read, update, archive, search, and batch-process invoice records, and associate invoices with the contacts, companies, deals, and line items they belong to. It is intended for synchronising invoice data between HubSpot and external billing systems and for building invoice-aware sales workflows inside HubSpot.
11 endpointsLeads
The HubSpot CRM Leads API exposes the lead object that sits between contacts and deals in the HubSpot Sales Hub prospecting workspace. It supports create, read, update, archive, batch operations, and property-filtered search for lead records, allowing integrations to push prospect data into the prospecting queue and update qualification status as agents or reps progress them. It is the right entry point for connecting a SDR tool, lead-routing engine, or scoring model to HubSpot's prospecting workflow.
10 endpointsLine Items
The HubSpot CRM Line Items API manages the priced rows that compose deals, quotes, invoices, and subscriptions in HubSpot Commerce. It exposes single-record CRUD, batch read, batch create, batch update, batch upsert, batch archive, and search for line item records with full property and association support. Use it to build a quote out of products, attach line items to a deal during pipeline progression, or sync line-level pricing data between HubSpot and an external billing or e-commerce system.
11 endpointsListings
The HubSpot CRM Listings API provides a generic, object-type-parameterised CRUD and search interface for any standard or custom object in the portal. Endpoints accept an objectType path parameter so the same operations work for contacts, companies, deals, line items, products, tickets, quotes, listings, and any custom object schema the portal has defined. Use it when an integration or agent needs to operate over many object types from a single set of operations rather than wiring per-object endpoints.
11 endpointsLists
The HubSpot CRM Lists API manages static and active (filter-defined) lists for any CRM object — contacts, companies, deals, custom objects. It supports list creation, deletion, renaming, filter-definition updates, membership add and remove, search across lists, folder organisation, and translation between legacy and modern list IDs. Use it to build segmentation logic, drive marketing or workflow membership, or programmatically curate audiences for downstream automation.
25 endpointsMeetings
The HubSpot CRM Meetings API manages the meeting engagement object that records calendar interactions between reps and contacts in the HubSpot CRM. It supports single-record CRUD, batch read, batch create, batch update, batch upsert, batch archive, and search across meeting properties and associations. Use it to log meetings from an external calendar, sync meeting outcomes back into HubSpot, or surface meeting history on a contact or deal timeline.
11 endpointsNotes
The HubSpot CRM Notes API manages the note engagement object that captures free-text annotations on contacts, companies, deals, and tickets in HubSpot. It supports single-record CRUD, batch read, batch create, batch update, batch upsert, batch archive, and search across note properties and associations. Use it to log AI-generated meeting summaries, sync notes from a sales engagement tool, or surface annotation history on a contact timeline.
11 endpointsPartner Clients
The HubSpot Partner Clients API exposes the partner_clients CRM object that HubSpot Solutions Partners use to track the customer accounts they have referred or are managing. It supports reading individual partner client records, listing partner clients with pagination, batch read and batch update of up to 100 records per call, and a search endpoint for filtering by property. The API does not expose create or archive operations because partner client records are provisioned through HubSpot's partner enrollment flow rather than directly via the API. Use it to audit your partner book of business, sync partner client metadata into a partner portal, or drive reporting on referred accounts.
6 endpointsPayments
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.
4 endpointsPostal Mail
The HubSpot Postal Mail API treats postal mail engagements — direct mail letters, postcards, packages — as first-class CRM records that can be logged against contacts, companies, and deals. It supports the standard CRM object pattern: read, list, patch, and archive single records, plus batch read, create, update, and archive of up to 100 records per call, and a search endpoint with filter groups and sort. Use it to log direct mail sends from a print partner back into the CRM, build outreach reports that combine digital and offline channels, and trigger follow-up sequences once a piece of postal mail is delivered.
11 endpointsProperties
The HubSpot CRM Properties API manages the schema layer that sits behind every CRM object — the named fields stored on contacts, companies, deals, tickets, and custom objects. It exposes endpoints to create, read, update, and archive properties for any object type, organise them into property groups, and run batch read or archive operations. Use it to bootstrap the custom fields a portal needs, keep the field schema in sync with another system of record, document the field model for compliance reviews, and clean up unused properties after a redesign. Read access works without write scopes, so agents that only need to introspect the schema can stay scoped down.
13 endpointsQuotes
The HubSpot CRM Quotes API lets sales teams and integrations programmatically create, read, update, archive, and search Quote records — the documents that capture proposed pricing, terms, and line items presented to a buyer. Each quote is a CRM object that can be associated with deals, contacts, companies, line items, and signatures, and supports custom properties just like other HubSpot CRM objects. The API exposes single-record CRUD, batch create, batch read, batch update, batch upsert, batch archive, and a search endpoint with filtering and sorting.
11 endpointsServices
The HubSpot CRM Services API provides a generic CRUD, batch, and search interface over any HubSpot CRM object type — including standard objects (companies, contacts, deals, line items, products, tickets, quotes) and custom objects defined via the Schemas API. Endpoints are templated on /crm/v3/objects/{objectType} so a single integration pattern works for every object type in the portal. The API supports single-record operations (read, update, archive), batch read, batch create, batch update, batch upsert by unique property, batch archive, and a full-featured search with filters, sorting, and paging.
11 endpointsTaxes
The HubSpot CRM Taxes API manages Tax records — the named tax rates that HubSpot Commerce applies to line items on quotes, invoices, and subscriptions. Each Tax record has a label, rate, and optional jurisdiction metadata, and can be associated with the line items it applies to. The API exposes single-record CRUD, batch read, batch create, batch update, batch upsert by unique property, batch archive, and a search endpoint with filters and sorting.
11 endpointsTickets
The HubSpot CRM Tickets API manages support ticket records — the customer issues that flow through HubSpot Service Hub pipelines. Tickets have status, priority, owner, source, and category properties, and can be associated with contacts, companies, deals, conversations, and any custom CRM object. The API exposes single-record CRUD, batch read, batch create, batch update, batch upsert by unique property, batch archive, ticket merge, and a search endpoint with full filter, sort, and paging support.
12 endpointsTimeline
The HubSpot CRM Timeline API lets a public app create custom timeline events that appear on the timeline of CRM records — contacts, companies, tickets, and deals. Apps first define event templates that describe the event type, header, detail, and tokens (event-specific fields), then emit individual events that bind values to those tokens. The API supports template management (create, list, get, update, delete event templates), token management on a template, single and batch event creation, and rendering of an event's header and detail as HTML for display inside HubSpot.
13 endpointsUsers
The HubSpot CRM Users API exposes the User CRM object, which represents end users tracked alongside contacts, companies, and deals (distinct from the HubSpot account owners managed by the Users Provisioning API). Each User record supports custom properties, associations to other CRM objects, and the standard CRM object operations. The API includes single-record CRUD, batch read, batch create, batch update, batch upsert by unique property, batch archive, and a search endpoint with filters and sorting on /crm/v3/objects/users.
11 endpointsConnect Your Agent
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.