Official vendor OpenAPI document · agent-readyCRMContact Managementoauth2,apiKey13 EndpointsREST
For Agents
Manage the field schema for any HubSpot CRM object - create, read, update, archive, and group custom and standard properties.
Use for: I need to add a custom enumeration property to the contacts object, List all properties defined on the deals object, Read the definition of a specific contact property, Update the options on an enumeration property
Not supported: Does not read or write property values on records, run validation, or manage permissions - use for HubSpot CRM property schema and groups only.
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.
Install Jentic One Beta
Connect the Properties to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Properties, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-crm-properties" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-crm-properties" | 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 Properties API.
Create a custom property on a CRM object type with a chosen field type and options
Read a single property's full definition by name
Update a property's label, description, options, or display order
Archive a property from a CRM object type
List all property groups for an object type and create new ones
Batch read or batch archive up to 100 properties per call
Use Cases
Patterns agents use Properties API for, with concrete tasks.
★ Bootstrap a portal's custom fields
When onboarding a new HubSpot portal, create the custom properties the team needs in a single scripted run. POST /crm/v3/properties/{objectType} creates each property with its field type, label, and options, and PATCH /crm/v3/properties/{objectType}/groups/{groupName} keeps property groups in shape. The result is a portal with a known field model rather than ad hoc clicks in the UI.
POST /crm/v3/properties/contacts with name=lead_score, label='Lead Score', type=number, fieldType=number to create the property.
Schema drift detection
Compare a portal's live property model against an expected schema definition. List the properties on each object type, diff against a JSON definition stored in source control, and surface drift for review. Useful for governance teams that need to keep multiple portals aligned.
GET /crm/v3/properties/contacts to list every property on the contacts object and compare each name against the canonical schema.
Property cleanup after a redesign
Archive properties that are no longer in use after a CRM redesign. POST /crm/v3/properties/{objectType}/batch/archive accepts up to 100 property names per call. Pair with a pre-flight read to confirm no workflows depend on each property before archiving.
POST /crm/v3/properties/deals/batch/archive with the names of 30 deprecated properties.
AI agent execution through Jentic
An agent that needs to manage the schema discovers this API via Jentic's intent search using a query like 'create a hubspot custom property' or 'list hubspot contact properties', loads the input schema for the chosen operation, and executes the call with credentials supplied from your Jentic One instance. The same flow handles batch read, group management, and archive.
Search Jentic for 'create a hubspot custom property', load POST /crm/v3/properties/{objectType}, and execute it for objectType=contacts with a property definition payload.
Key Endpoints
13 endpoints — 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.
METHOD
PATH
DESCRIPTION
GET
/crm/v3/properties/{objectType}
List properties for an object type
POST
/crm/v3/properties/{objectType}
Create a property on an object type
GET
/crm/v3/properties/{objectType}/{propertyName}
Read a single property's definition
PATCH
/crm/v3/properties/{objectType}/{propertyName}
Update a property's label, options, or group
DELETE
/crm/v3/properties/{objectType}/{propertyName}
Archive a property from an object type
POST
/crm/v3/properties/{objectType}/batch/read
Read up to 100 properties in one call
POST
/crm/v3/properties/{objectType}/batch/archive
Archive up to 100 properties in one call
GET
/crm/v3/properties/{objectType}/groups/{groupName}
Read a property group definition
GET
/crm/v3/properties/{objectType}
List properties for an object type
POST
/crm/v3/properties/{objectType}
Create a property on an object type
GET
/crm/v3/properties/{objectType}/{propertyName}
Read a single property's definition
PATCH
/crm/v3/properties/{objectType}/{propertyName}
Update a property's label, options, or group
DELETE
/crm/v3/properties/{objectType}/{propertyName}
Archive a property from an object type
POST
/crm/v3/properties/{objectType}/batch/read
Read up to 100 properties in one call
POST
/crm/v3/properties/{objectType}/batch/archive
Archive up to 100 properties in one call
GET
/crm/v3/properties/{objectType}/groups/{groupName}
Read a property group definition
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
Properties
- Foundational (C)54/100
72
Foundational Compliance69
Developer Experience & Jentic Compatibility28
AI-Readiness & Agent Experience94
Agent Usability70
Security83
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
72
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
88%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
69
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
30%
Example Density
How richly the API is illustrated with examples.
95%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
28
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
46%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
65%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
70
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
70%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
83
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
83%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Properties by hand means implementing HubSpot's OAuth2 authorization-code flow (or managing a private-app header token), sending each call to api.hubapi.com with the correct objectType in the path and field-type and options payloads, and handling token refresh yourself. Through Jentic you install once, import Properties from the API Directory, store the token once, and your agent calls it.
Permission scoping
This API puts the object type in the URL path (/crm/v3/properties/{objectType}/...), so a rule can pin your agent to one object type: it can read and manage that type's property schema and no other. You choose the operations it may call, so destructive ones like property delete or batch archive are not included unless you add them.
Credential isolation
Your HubSpot token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a HubSpot custom property' or 'list properties for a contact', and Jentic returns the matching Properties operation with its input schema, including the field-type and options structure, so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Properties API through Jentic.
What authentication does the HubSpot Properties API use?
It accepts OAuth 2.0 access tokens and private app access tokens passed as a Bearer credential in the Authorization header. Schema write operations require scopes that match the target object type.
Can I create an enumeration property with custom options?
Yes. POST /crm/v3/properties/{objectType} with type=enumeration, fieldType=select (or radio/checkbox), and an options array specifying each option's label, value, and displayOrder.
What are the rate limits for the HubSpot Properties API?
It shares HubSpot's account-level rate limits, typically 100 requests per 10 seconds for OAuth apps. Schema changes are infrequent enough that the standard limits are rarely a concern.
How do I list every property on a HubSpot object through Jentic?
Search Jentic with 'list hubspot properties', load GET /crm/v3/properties/{objectType}, and execute it with the object type set to the resource you care about (contacts, companies, deals, tickets, or a custom object name).
Is the HubSpot Properties API free?
It is included with all HubSpot accounts that have CRM access enabled. There is no per-call fee; the standard account-level rate limits apply.
How do I move a property to a different group?
PATCH /crm/v3/properties/{objectType}/{propertyName} with a groupName field set to the new group's internal name. The property's display position then follows the order configured on the new group.
Can I limit what my agent is allowed to do with the HubSpot Properties API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which Properties operations and which HubSpot credential your agent may use. Since the object type sits in the URL path (/crm/v3/properties/{objectType}), you can pin the agent to a single object type, letting it read and manage that type's schema and no other. You also choose the specific operations it can call, so destructive ones like archiving a property (DELETE /crm/v3/properties/{objectType}/{propertyName}) or batch archive are excluded unless you explicitly grant them.
GET STARTED