Properties

Name: Properties API
Brand: Properties
Availability: InStock

✓ Official Vendor SpecCRMContact Managementoauth2,apiKey13 EndpointsREST

For Agents

Manage the field schema for any HubSpot CRM object — create, read, update, archive, and group custom and standard properties.

Quickstart

Get started with Properties in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a hubspot custom property"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

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

GET STARTED

Start building with Properties API

Explore with Jentic

View OpenAPI Document

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.

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 the Jentic vault. 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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

HubSpot OAuth and private app tokens live encrypted in the Jentic vault. Schema-write scopes are checked at execution time, and the Authorization header is attached server-side so the token never enters agent context.

Intent-based discovery

Agents search by intent (e.g. 'create a hubspot custom property' or 'list hubspot properties') and Jentic returns the matching Properties operation with its JSON Schema, including the field-type and options structure.

Time to first call

Direct integration: half a day to wire OAuth, schema validation, and group management. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot CRM Property Validations

Reads the validation rules attached to properties managed here

Use after creating a property to inspect any validation rules HubSpot has applied to it.

Complementary

HubSpot CRM Custom Objects

Defines the custom object types whose properties this API then manages

Pick this when you need to create the object type itself before adding properties to it.

Complementary

HubSpot CRM Objects

Reads and writes the records that store values for the properties defined here

Use to populate values into the properties this API has defined.

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.