HubSpot API and custom development is how teams extend HubSpot beyond its built-in tools using code. Developers call the CRM API to read and write records, add custom-coded actions inside workflows, and build private or public apps that connect HubSpot to other systems. The result is a CRM that fits a process no standard setting can cover.
New contact
Set lifecycle stage
Score high → Sales
Score low → Nurture
What it does
Where code picks up where settings stop
The API and custom development handle the logic, data, and integrations that point-and-click setup cannot reach.
CRM API access
Read, create, and update contacts, companies, deals, tickets, and custom objects from outside HubSpot.
Custom-coded workflow actions
Run JavaScript or Python inside a workflow to calculate, format, or call an external service mid-process.
Private apps
Scoped access tokens for one-off internal integrations, replacing the older API key model.
Webhooks and subscriptions
Get notified the moment a record changes so an external system can react in near real time.
UI extensions
Add custom cards and tools to the record sidebar so reps see external data without leaving HubSpot.
Custom objects and properties via code
Define and populate data structures programmatically for models that standard objects do not cover.
How to use it
A practical path from idea to live
-
Confirm the gap is realCheck whether workflows, custom objects, or a native integration already solve the need before writing any code.
-
Create a private appIn Settings, build a private app and grant only the scopes the project requires, then generate the access token.
-
Build and test against the APIUse the CRM API or a custom-coded workflow action, validating against a test portal or sandbox first.
-
Add webhooks or UI extensions if neededSubscribe to record changes for live syncs, or surface external data inside the record view for your team.
-
Monitor and documentWatch API call usage against your tier limits, log failures, and document the build so it stays maintainable.
Related
Build on the custom apps foundation
API work usually sits inside a wider custom app and CRM strategy, so these pages connect the pieces.
FAQ
Common questions
When should I build with the API instead of configuring HubSpot?
Configure first. Workflows, custom objects, custom properties, and native integrations cover most needs without code. Reach for the API when you need logic HubSpot cannot express, a two-way sync with a system that has no native connector, or data shown inside HubSpot from an outside source. Building adds maintenance, so it should earn its place.
What is a custom-coded workflow action?
It is a step inside a HubSpot workflow where you write JavaScript or Python that runs against the enrolled record. Teams use it to calculate values, reformat data, or call an external service in the middle of an automation. It needs a Hub that includes programmable automation, typically the higher tiers, and a developer to maintain the code.
Do I still need an API key?
No. HubSpot moved away from a single account-wide API key toward private apps, which use scoped access tokens. A private app lets you grant only the permissions a project needs and revoke them without affecting other integrations, which is safer for production work.
What are the API rate limits I should plan around?
HubSpot applies limits on calls per second and per day, and the daily allowance scales with your subscription tier and any API add-on. Directionally, higher tiers and the add-on raise the ceiling. For a SEA team syncing LINE conversations or e-commerce orders at volume, design for batching and retries rather than firing one call per record.
Can custom development connect HubSpot to local tools like LINE?
Yes. Many teams in Thailand and across Southeast Asia use the API and webhooks to bridge HubSpot with channels and systems that lack a native connector, including LINE messaging, regional payment platforms, and local logistics tools. A private app handles the auth, and webhooks keep both sides current.