Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / CRM / Hubspot / CRM Object Library
CRM Object Library logo

HubSpot CRM Object Library

Browse all Hubspot APIs
48
AI ReadinessFoundational (D+)48/100
See full scorecard
Official vendor OpenAPI document · agent-readyCRMContact 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.

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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the CRM Object Library to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CRM Object Library, 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-object-library" | sh
2

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-object-library" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 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

Inform onboarding scripts that need to confirm object availability before configuring workflows

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

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.

C

CRM Object Library

- Foundational (D+)
48/100
74
Foundational Compliance
67
Developer Experience & Jentic Compatibility
23
AI-Readiness & Agent Experience
94
Agent Usability
70
Security
63
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
96%

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.

67

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4
17%

Example Density

How richly the API is illustrated with examples.

100%

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.

23

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
42%

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.

50%

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).

63

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1
62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring HubSpot CRM Object Library by hand means implementing its OAuth2 authorization-code flow (or managing a private-app token), routing read calls to api.hubapi.com, and parsing the enablement response yourself. Through Jentic you install once, import HubSpot CRM Object Library from the API Directory, store the token once, and your agent calls it.

Permission scoping

These endpoints are read-only enablement lookups, with the object type id in the URL path (/crm/v3/object-library/enablement/{objectTypeId}) on the single-object read. Limit the agent to the operations it needs, such as reading enablement status, so it only queries the object enablement you intend.

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 'check HubSpot object enablement', and Jentic returns the matching enablement operation with its response schema so the agent calls the right endpoint without browsing the reference docs.

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.

Can I limit what my agent is allowed to do with the HubSpot CRM Object Library API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which operations and credentials your agent may use. This API exposes only two read-only enablement lookups: reading the enablement state of all object types, and reading a single object type by its objectTypeId in the path. You can restrict the agent to just the operations it needs, such as the read-all enablement call, so it only queries the object enablement you intend and never reaches other HubSpot endpoints.

GET STARTED

Start building with CRM Object Library API

Explore with Jentic One
View OpenAPI Document