The Engagements API will be undergoing maintenance between 5:00 PM and 6:00 PM Eastern Time Sunday, September 15. During this maintenance period, there will be a brief period where the Engagements API will be unavailable, and any requests to the API will result in 500 errors. We expect this period...
For this week’s round up we rolled 3 updates together with an improved experience in the developer tools and 2 APIs moving from developer preview to general availability.
Data privacy is a top priority at HubSpot, and helping our developer community stay on top of data compliance is important to us. HubSpot users have the ability to permanently delete a contact record to comply with privacy laws. You can see more details about this feature in this help article: ...
For this post we rolled 5 updates into one with a new header to help with Webhook validation, a new callback for embedded forms, added flexibility for content developers, a number of documentation updates, and a small update to the Developer’s Terms of Service.
Update: Maintenance is complete!
The Timeline API will be undergoing maintenance between 5:00 PM and 6:00 PM Eastern Time Sunday, August 11. During this maintenance period, there will be a brief period where the Timeline API will be unavailable, and any requests to the API will result in 503...
Update: These changes are now live, and the
demo API key will only be allowed to make GET requests.
When HubSpot launched our first public APIs in 2010, we created our public API demo account so that developers would have an account that could be used to test those new APIs. This was years before...
Today we are announcing three new updates to Developer Accounts. A new home screen for Developer Accounts, masking the client secret, and adding an option to specify a redirect URL for your applications.
We’re experimenting with batching sunset updates every other week. We hope this will improve your experience as a developer community. Please let us know what you think using the community links below.
Edit: This is now live. If you have any questions or comments, join the discussion on our forum post
We’re excited to share that in the coming weeks, HubSpot will be making some significant changes to our API Limits for all developers, customers, and users of HubSpot.
Update: These changes are now live
Today, we’re releasing a new attribute to the
context object within the forms v3 endpoint which enables users to enroll contacts directly into goToWebinar webinars via the API.
To maintain the privacy of contacts within the HubSpot database, we will be sunsetting the ability to pull the IP address of Contacts via HubSpot’s API or the exports of email event (emailEvents) records.
Geo-location data (e.g. city, state, region, country, timezone, etc.)...
In an effort to enforce the highest security standards, basic authentication is being removed from webhooks within workflows. There’s a new, more secure way to help you verify your webhook requests coming from HubSpot. This is done with request signatures. Using request...
In an effort to enforce the highest security standards, basic authentication is being removed from webhooks. There’s a new, more secure way to help you verify your webhook requests coming from HubSpot. This is done with request signatures. Using request signatures, HubSpot...
The original v1 of the Forms API was released in sync with the launch of our then new form tools. Since then, we've added several new features to our forms, including support for progressive and dependant fields, support for inline thank you messages, and new styling options for columns and rows...
Update: The HubSpot Developers Forum has been fully migrated to community.hubspot.com. The older Developer Forums on integration.hubspot.com are now read-only.
When the HubSpot CRM originally launched, contacts could only be associated with a single company. This association was done using the
associatedcompanyid, since only a single association from a contact to a single company was supported. Since then, we've added new objects, such as tickets and...
Today, we're releasing a new endpoint for our Forms API that will let you get the details for individual submissions for a HubSpot form. This will include all of the fields included in the submission, as well as the time that the form was submitted and the page that the form was...
Previously users of the Native Shopify integration and the ecommerce bridge APIs were provided with three out-of-the-box ecommerce workflows that were hard-coded to 3 email triggers and 3 time delays. Moving forward, users will have complete flexibility to customize their embedded...
Along with a portal’s Timezone (e.g. US/Eastern), the `/integrations/v1/me` endpoint now returns UTC Offset information, which should make it easier for developers to localize timestamps that HubSpot’s API returns. Going forward, this endpoint will include a human readable...
Beginning on January 7, the developer forums will be migrated from integrate.hubspot.com to community.hubspot.com --- the same platform as the HubSpot customer and CMS developer forums. The migration will conclude on January 29th.
Today we're releasing a new endpoint for the Analytics API. This endpoint will let you check to see if there is existing analytics data for any of the specific objects supported by the Analytics API. This will allow you to perform a quick check to see if data exists before making...
Update: The deadline to migrate existing HTTP webhook URLs is being moved from Tuesday, December 4th 2018 to Tuesday, January 15th 2019.
Ask technical questions and get answers! Join us for this free, virtual developer event on Wednesday - December 12th, 2018 at 9 am PT / 12pm ET. Submit your technical questions in advance and a panel of HubSpot development experts will answer them in detail.
Today, we're releasing a few new features for the Ecommerce Bridge to help you track down sync errors. We're releasing two new endpoints, and adding additional functionality to the existing sync errors endpoint to make it easier to find specific errors.
This is a reminder that the previously announced issue where some HTTP requests that should result in an error response are incorrectly returning HTTP 200 status codes will be going live tomorrow morning (November 13 2018).
Sunset: "quota" field will no longer be provided by the Owners API
New feature: Check the sync status of a specific object
New feature: Rate limit information headers
All new webhook URLs are required to use HTTPS, and all existing URLs will be required to use HTTPS starting December 4th.
Join us on October 26th at 9 am PT / 12 pm ET for an overview of the latest developer releases and an AMA with members of our product and engineering teams who will be available to answer any of your questions!
We've identified an issue where certain requests that should result in an error response are incorrectly returning responses with HTTP 200 status codes and an empty response body.
New Marketing Professional portals will no longer have access to the workflow webhook action starting November 1st. New Marketing Enterprise and existing Marketing Professional portals will continue to have access going forward.
New functionality: Ability to manage parent <-> child company relationship via API
New functionality: Programmable actions for bots
New Functionality: Workflow performance metrics endpoint
Integrators can add support information to their in-app listing via their app settings in their developer portal
New endpoint: Get Lifecycle Stage metrics
Timeline event properties of type 'string' now support 'does not contain', 'starts with', 'ends with', 'is known', and 'is unknown' filters when creating lists.
redirect_uri can now be served over http if the host is
The old form embed code is being deprecated and replaced with the new embed code.