The API is built to allow you to create a functional application or integration quickly and easily. We know from experience - these are the APIs that power the HubSpot application. The ecosystem of developers creating integrations on top of the APIs is strong and diverse, ranging from webinar providers to CRMs to social advertising.
All of the HubSpot APIs are organized around REST - if you've interacted with a RESTful API already, many of the concepts will be familiar to you. All API calls to HubSpot should be made to the https://api.hubapi.com base domain. We use many standard HTTP features, like HTTP verbs, which can be understood by many HTTP clients. JSON will be returned in all responses from the API, including errors. The APIs are designed to have predictable, straightforward URLs and to use HTTP response codes to indicate API errors.
If you're considering an integration with HubSpot for commercial use - i.e. installation by mutual customers - you can learn more how to get certified and featured by HubSpot here.
The API allows for two means of authentication, OAuth and API keys. See our Authentication Overview for more details about authenticating requests.
API keys are great for rapid prototyping, but for security and commercial use, all integrations should strive to use OAuth. The best way to get started is by implementing one of these two methods of authentication, both of which you can test out quickly in our demo portal:
Individual HubSpot accounts (portals) are also subject to some rate limiting - you can see our full API guidelines here. When you've moved past playing with the API and are ready to start developing in earnest, you can create your OAuth credentials and a sandboxed environment for you to test your use of the API with and register an application with HubSpot by creating a developer account:
If you've ever got questions, feel free to check out our developer forum or to leave us some feedback using the Submit Feedback button throughout the site.