HubSpot APIConnect HubSpot without building on its API
HubSpot has a REST API. Self-serve for any developer; rate limits scale with the installing account's tier (Free/Starter, Professional, Enterprise). If you're reading the docs because you need HubSpot to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across HubSpot and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessSelf-serve
What the HubSpot API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 (public apps) or static access token (private/single-account apps)
- Who can get access
- Self-serve for any developer; rate limits scale with the installing account's tier (Free/Starter, Professional, Enterprise).
- What it covers
- CRM objects (contacts, companies, deals, tickets), associations, marketing and other hub data.
- Limits
- Private apps get 100 requests/10s (Free/Starter) or 190/10s (Pro/Enterprise) with daily caps of 250k/625k/1M, and public OAuth apps get 110 requests/10s per installing account.
Official docs: developers.hubspot.com. Checked September 2026. Vendors change access terms, so confirm with HubSpot before you build.
Building on the HubSpot API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get HubSpot credentials, and manage tokens and refreshes. | Connect your HubSpot account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the HubSpot task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting HubSpot work off someone's desk, the build is the slow part.
What teams usually want the HubSpot API for
Lead-to-onboarding
When a HubSpot deal closes, Caddi opens the onboarding workspace, sends the welcome packet, and creates the onboarding tasks.
Meeting note write-back
Caddi turns each meeting transcript into a structured HubSpot activity and opens follow-ups on the right deal.
Document fan-out
When a signed contract returns, Caddi files it, updates the HubSpot deal, and notifies the deal owner.
HubSpot API questions
Does HubSpot have an API?
Yes. HubSpot has a REST API, authenticated with OAuth 2.0 (public apps) or static access token (private/single-account apps). The official documentation is at https://developers.hubspot.com/docs.
How do I get access to the HubSpot API?
Self-serve for any developer; rate limits scale with the installing account's tier (Free/Starter, Professional, Enterprise).
Does the HubSpot API have rate limits?
Private apps get 100 requests/10s (Free/Starter) or 190/10s (Pro/Enterprise) with daily caps of 250k/625k/1M, and public OAuth apps get 110 requests/10s per installing account.
Can I connect HubSpot to my other tools without writing code against its API?
Yes. With Caddi you show the HubSpot task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across HubSpot and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate HubSpot with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for HubSpot is reviewed before it runs in production, and every run is logged.
Connect HubSpot without the build.
Drop your work email and pick a time. We'll show you Caddi running your HubSpot workflow end to end.