HubSpot CRM Schemas
Browse all Hubspot APIs✓ Official Vendor SpecCRMContact Managementoauth27 EndpointsREST
For Agents
Define and manage HubSpot custom object schemas — properties, primary display, and associations — so an agent can model bespoke CRM data structures and link them to standard objects.
Use for: I need to define a custom object schema for tracking equipment in HubSpot, Add a new property to an existing custom object schema, List all custom object schemas configured in this HubSpot portal, Create an association between my Equipment custom object and the Companies object
Not supported: Does not handle individual record CRUD, property values, or workflow automation — use for defining custom object types, their properties, and their schema-level associations only.
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.
Install Jentic One Beta
Connect the HubSpot CRM Schemas to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HubSpot CRM Schemas, 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 HubSpot CRM Schemas API.
List every custom object schema in the portal with GET /crm-object-schemas/v3/schemas
Define a new custom object schema including properties and required fields via POST /crm-object-schemas/v3/schemas
Read the current definition of a schema by objectType using GET /crm-object-schemas/v3/schemas/{objectType}
Evolve a schema with additional properties or display rules using PATCH /crm-object-schemas/v3/schemas/{objectType}
Add an association between two custom object schemas with POST /crm-object-schemas/v3/schemas/{objectType}/associations
Remove a schema-level association via DELETE /crm-object-schemas/v3/schemas/{objectType}/associations/{associationIdentifier}
Delete an obsolete schema with DELETE /crm-object-schemas/v3/schemas/{objectType}
Use Cases
Patterns agents use HubSpot CRM Schemas API for, with concrete tasks.
★ Modelling Industry-Specific Data With Custom Objects
When standard HubSpot objects (contacts, companies, deals, tickets) cannot represent industry-specific entities — like loans for a lender, vehicles for a dealership, or properties for a real-estate firm — teams use the Schemas API to define custom objects with the exact properties and display rules they need. Defining a schema is a one-time setup; once created, custom objects behave like standard objects with full CRUD, search, and association support across HubSpot.
Call POST /crm-object-schemas/v3/schemas with name, labels, primaryDisplayProperty, requiredProperties, and a properties array defining each field for the new custom object.
Schema Evolution as Business Requirements Change
Business processes change, and existing custom objects need new fields or relationships over time. The Schemas API supports incremental updates via PATCH /crm-object-schemas/v3/schemas/{objectType} so engineers can add properties or update display configuration without recreating the schema. Combined with the associations endpoints, teams can also wire up new relationships (e.g., link a custom Project object to Deals) when the business model expands.
Call PATCH /crm-object-schemas/v3/schemas/{objectType} with an object containing the new property definitions and any updated display configuration.
Connecting Custom Objects to Standard CRM Records
Custom objects are most useful when they relate to standard records — for example, a custom Subscription object linked to Companies and Deals so renewal data shows up in the right CRM views. POST /crm-object-schemas/v3/schemas/{objectType}/associations creates these schema-level associations, which then become available for object-level association calls. DELETE on the same path with an associationIdentifier tears the link down when needed.
Call POST /crm-object-schemas/v3/schemas/p_subscription/associations with fromObjectTypeId='p_subscription' and toObjectTypeId='0-2' to associate a Subscription custom object with Companies.
AI Agent Bootstrapping a New HubSpot Tenant
An onboarding agent provisions a fresh HubSpot portal for a new customer by reading their data model from a config file and creating each custom object schema in turn. Through Jentic the agent searches for schema operations, loads the create and association schemas, and executes them in dependency order. Jentic stores the OAuth credentials in its vault so the agent only sees scoped execution tokens.
Search Jentic for 'create hubspot custom object schema', load the operation, and execute POST /crm-object-schemas/v3/schemas for each entry in the customer's data model config.
Key Endpoints
7 endpoints — the hubspot crm schemas api defines how custom objects store and represent information in the hubspot crm.
METHOD
PATH
DESCRIPTION
GET
/crm-object-schemas/v3/schemas
List all custom object schemas
POST
/crm-object-schemas/v3/schemas
Create a new custom object schema
GET
/crm-object-schemas/v3/schemas/{objectType}
Get a schema by objectType
PATCH
/crm-object-schemas/v3/schemas/{objectType}
Update a schema
DELETE
/crm-object-schemas/v3/schemas/{objectType}
Delete a schema
POST
/crm-object-schemas/v3/schemas/{objectType}/associations
Create an association between schemas
DELETE
/crm-object-schemas/v3/schemas/{objectType}/associations/{associationIdentifier}
Remove a schema association
GET
/crm-object-schemas/v3/schemas
List all custom object schemas
POST
/crm-object-schemas/v3/schemas
Create a new custom object schema
GET
/crm-object-schemas/v3/schemas/{objectType}
Get a schema by objectType
PATCH
/crm-object-schemas/v3/schemas/{objectType}
Update a schema
DELETE
/crm-object-schemas/v3/schemas/{objectType}
Delete a schema
POST
/crm-object-schemas/v3/schemas/{objectType}/associations
Create an association between schemas
DELETE
/crm-object-schemas/v3/schemas/{objectType}/associations/{associationIdentifier}
Remove a schema association
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
HubSpot OAuth tokens with the crm.schemas.custom scopes are stored encrypted in the Jentic vault. Agents receive scoped execution tokens — the raw access token never enters agent context or logs.
Intent-based discovery
Agents search Jentic with intents like 'create hubspot custom object schema' and Jentic returns the matching Schemas operations with typed input schemas, so the agent can model new object types without browsing HubSpot's docs.
Time to first call
Direct HubSpot Schemas integration with OAuth and dependency-ordered schema/association calls: 1-3 days. Through Jentic: under an hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using HubSpot CRM Schemas API through Jentic.
What authentication does the HubSpot CRM Schemas API use?
It uses OAuth 2.0 with the crm.schemas.custom.read and crm.schemas.custom.write scopes, passed as a Bearer token in the Authorization header. Through Jentic the OAuth token is stored encrypted in the vault and injected at execution time so the agent never holds the raw secret.
Can I add a new property to an existing custom object with the Schemas API?
Yes. PATCH /crm-object-schemas/v3/schemas/{objectType} accepts a body that adds new property definitions to the schema. Property name, label, type, and groupName are required for each new property.
What are the rate limits for the HubSpot CRM Schemas API?
HubSpot enforces 100 requests per 10 seconds for OAuth apps and 190 per 10 seconds for private apps on Enterprise tiers, plus daily quotas. Schema operations are typically infrequent (setup time and occasional changes) so rate limits rarely bind in practice.
How do I create a custom object schema through Jentic?
Search Jentic for 'create hubspot custom object schema', load the POST /crm-object-schemas/v3/schemas operation, and execute it with name, labels, primaryDisplayProperty, requiredProperties, and a properties array. Jentic validates the input against the typed schema before sending.
Can I delete a custom object schema once it has records?
HubSpot only allows deleting a schema after all records of that object type have been archived. Use the Custom Objects API to archive existing records first, then call DELETE /crm-object-schemas/v3/schemas/{objectType}.
How do schema-level associations differ from record-level associations?
A schema-level association declares that two object types can be related (created via POST /crm-object-schemas/v3/schemas/{objectType}/associations). A record-level association uses the Associations API to link two specific records once the schema-level association exists. Both are required for end-to-end relationship modelling.
GET STARTED