How to Get Your HubSpot API Key (and What to Build With It)

How HubSpot API access works, what the HubSpot API lets you connect, and when you need a developer to do it properly. Perth, Melbourne, Sydney and Brisbane.

Best for: Sales and marketing managers, operations managers Practical guide for business decision-makers

Who this is for

Sales and marketing managers, operations managers who want to connect HubSpot to other systems and need to understand how its API works before committing to anything.

Question this answers

How do I get HubSpot API access and what can I actually connect HubSpot to?

What you'll leave with

  • How HubSpot authenticates API access
  • What data the HubSpot API exposes
  • Whether no-code tools cover your use case
  • What a proper HubSpot API integration involves
  • When you need a developer and when you do not

How HubSpot API access works

HubSpot uses a private app access token created inside your HubSpot account. The exact screens move around as HubSpot updates its interface, so rather than repeat a menu path that may already be out of date, the reliable source is the official documentation: HubSpot developer documentation.

HubSpot retired its old API keys in late 2022. Private app tokens replaced them and are scoped, so a token only reaches the objects you allow. Anything acting for other HubSpot accounts uses OAuth instead.

Treat API credentials like a password. Anyone holding them can read and often write data in your HubSpot account. Do not paste them into untrusted tools, and do not send them over email or chat.

What the HubSpot API lets you do

The HubSpot API gives you programmatic access to the core data in your account. Broadly that covers:

  • Contacts, companies, deals and tickets
  • Custom objects and custom properties
  • Pipelines and deal stages
  • Marketing emails, forms and campaign data
  • Quotes, line items and products
  • Associations between any of the above

With that access you can push data into accounting or reporting systems, keep records in step across tools, and build dashboards from live HubSpot data rather than from exports someone has to remember to run.

HubSpot and no-code tools

HubSpot has a native Zapier connector. For simple one-way automation, a Zap is often the right answer and costs a fraction of a build. HubSpot has a strong Zapier connector, which handles most simple field-to-field automation.

Building with the HubSpot API

Connecting HubSpot to another system means working through five things, in roughly this order:

  1. Authenticate using the credentials above, and store them somewhere your team can rotate
  2. Map the data, deciding what moves between HubSpot and the other system, in which direction, and triggered by what
  3. Handle the edge cases, such as a record that already exists on one side but not the other, or a partially completed transaction
  4. Build error handling, so a failed call is retried or surfaced rather than silently dropped
  5. Set up monitoring, so you find out something stopped working before it becomes an accounting problem

A common pairing is HubSpot with Xero or MYOB. Read-only reporting is usually straightforward. Live two-way sync is where the mapping and error handling turn it into a proper development project.

When to bring in a developer

Some HubSpot API work is genuinely straightforward. Some is not. An honest split:

HubSpot automations you can set up yourself

  • Pushing website form submissions into HubSpot
  • Sending a Slack alert when a deal closes
  • Exporting a contact list for a campaign
  • Reading deal data into a reporting sheet

When your HubSpot setup needs a developer

  • Two-way sync between HubSpot deals and accounting invoices

    Deciding which system owns the customer record, and what happens when both change, is the hard part.

  • Migrating from another CRM while HubSpot is live

    Duplicate detection and association mapping decide whether the result is usable or a mess.

  • Custom object models

    HubSpot custom objects are powerful and easy to model badly in a way that is expensive to unwind later.

  • Attribution reporting across marketing and finance

    Joining HubSpot activity to actual revenue means reconciling two different definitions of a customer.

These integrations look simple from the outside. The work is in the detail: field mapping, conflict resolution, error recovery, and keeping everything in step as both HubSpot and the connected system change over time.

If the integration touches invoicing, stock or payroll, getting it wrong has real financial consequences. A properly built integration with monitoring and alerting is worth the upfront cost.

Key takeaways

  • HubSpot uses a private app access token created inside your HubSpot account
  • The API covers contacts, custom objects and custom properties, pipelines and deal stages and more
  • HubSpot has a native Zapier connector, which handles simple one-way flows
  • Simple read-only use cases are achievable without specialist help
  • Two-way sync with accounting or payroll is a development project, not a weekend task
HubSpotAPI IntegrationIntegrations

Ask the author

Question about the HubSpot API?

Ask it here and it comes straight to Kasun, who wrote this. No sales call, no obligation, and a real answer even if the answer is that you do not need us.

Kasun Wijayamanna, Founder Kasun Wijayamanna
Founder, replies within one business day

Get Started

Want help choosing the right next step?

Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.

Australian owned and operated

Built here. Your data stays here.

  • No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
  • Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
  • Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.