CRM Object Library

Name: CRM Object Library API
Brand: HubSpot CRM Object Library
Availability: InStock

✓ Official Vendor SpecCRMContact Managementoauth22 EndpointsREST

For Agents

Read which CRM object types are enabled in a HubSpot portal so an integration can route operations to enabled objects only.

Quickstart

Get started with CRM Object Library 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:
"list which HubSpot CRM object types are enabled in this portal"

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

Capabilities

What an agent can do with CRM Object Library API.

List the enablement state of every CRM object type available in the library for the connected portal

Read the enablement state of a single object type by its objectTypeId

Surface specialised objects shipped by HubSpot (appointments, courses, listings) that require explicit enablement

Drive integration discovery flows that decide which objects to operate against based on enablement

GET STARTED

Start building with CRM Object Library API

Explore with Jentic

View OpenAPI Document

Use for: Check whether the appointments object is enabled in this HubSpot portal, List every CRM object type and its enablement state, Find out if listings are available for write operations in this portal, Get the enablement status of a specific object by its type ID

Not supported: Does not handle object enablement changes, schema definition, or record-level CRUD — use for read-only object enablement discovery only.

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.

Use Cases

Patterns agents use CRM Object Library API for, with concrete tasks.

★ Integration Capability Discovery at Connect Time

When an integration first connects to a HubSpot portal, query the object library to learn which objects the portal can accept writes for. The response lets the integration enable or hide features (appointments scheduling, course enrolment, listings sync) based on portal capability rather than guessing or failing on a 403 from a write call. The discovery call typically runs once at connection time and is cached for the session.

Call GET /crm/v3/object-library/enablement at connect time, parse the response into a map of objectTypeId to enabled flag, and persist the map for the session.

Onboarding Wizard Pre-Flight

Drive an onboarding wizard that asks users which HubSpot features to wire up. Before showing a feature option, query the object library to confirm the underlying object is enabled in their portal, hiding options that would not work. This prevents setup failures and reduces support load on the integration vendor.

GET /crm/v3/object-library/enablement, then in the onboarding UI hide any feature whose corresponding objectTypeId returns enabled equals false.

Agent-Driven Capability-Aware Tool Routing

An AI agent operating across a HubSpot portal can call the object library at session start, learn which objects are enabled, and refuse to invoke tools that target disabled objects with a clear explanation back to the user. Through Jentic, the agent finds the read-all enablement operation by intent and uses the response to gate downstream tool calls.

GET /crm/v3/object-library/enablement and store the result; before any subsequent write call, look up the target objectTypeId and return a structured 'object not enabled' message if disabled.

Key Endpoints

2 endpoints — the hubspot crm object library api reports which crm object types are enabled in a given hubspot portal.

METHOD

PATH

DESCRIPTION

GET

/crm/v3/object-library/enablement

Read enablement state for all object types

GET

/crm/v3/object-library/enablement/{objectTypeId}

Read enablement state for a specific object type

GET

/crm/v3/object-library/enablement

Read enablement state for all object types

GET

/crm/v3/object-library/enablement/{objectTypeId}

Read enablement state for a specific object type

Why though Jentic?

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

Credential isolation

HubSpot OAuth and Private App tokens are stored encrypted in the Jentic vault. Agents receive scoped access references, never raw tokens.

Intent-based discovery

Agents search by intent (e.g., 'check HubSpot object enablement') and Jentic returns the read-all enablement operation with its response schema for parsing.

Time to first call

Direct integration: a few hours to handle the discovery call and cache. Through Jentic: under 15 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot CRM Schemas

Defines custom object schemas after enablement is confirmed

Use CRM-schemas to inspect or create custom object schemas once the Object Library confirms the object is enabled

Complementary

HubSpot Generic CRM Objects

Generic CRUD that operates over any object type the library reports as enabled

Use CRM-listings to write records to an object type once enablement has been confirmed

Complementary

HubSpot CRM Limits Tracking

Reports per-object record and property quotas for enabled objects

Pair with CRM-limitsTracking to confirm both enablement and headroom before bulk writes

FAQs

Specific to using CRM Object Library API through Jentic.

What authentication does the HubSpot Object Library API use?

OAuth 2.0 Bearer tokens or HubSpot Private App tokens in the Authorization header. Jentic stores the token encrypted in the vault and provides the agent with a scoped reference rather than the raw token.

Which object types appear in the response?

The response covers every CRM object type available in the library for that portal — standard objects (contacts, companies, deals), HubSpot-shipped specialised objects (appointments, courses, listings, services), and any custom object schemas defined in the portal — each with an enabled flag.

What are the rate limits for this API?

Standard HubSpot quotas apply: 100 requests per 10 seconds for OAuth apps and 110 for Private Apps, with daily caps that vary by Hub subscription. Because the response is small and changes rarely, integrations typically cache it for the connection session rather than calling it repeatedly.

How do I check object enablement through Jentic?

Run pip install jentic, call client.search('check HubSpot object enablement'), client.load to get the schema for GET /crm/v3/object-library/enablement, and client.execute. The response is a flat list of objectTypeId entries with their enabled state.

Does this API let me enable an object type?

No. The endpoints are read-only. Enabling a specialised object such as appointments or listings is done through the HubSpot UI or product-specific setup, not via this API.

What is the difference between this API and the CRM Schemas API?

The Object Library reports which object types are enabled in the portal. The CRM Schemas API defines the property and association shape of custom object types. Use the Object Library for capability discovery, and Schemas for actually creating or modifying custom object definitions.