In HubSpot, a ticket represents a customer request for help or support. The tickets endpoints allow you to manage this data and sync it between HubSpot and other systems. 

Tickets, along with companies, contacts, deals, line items, products, and quotes, are objects in the HubSpot CRM. Learn more about object properties, associations, relationships, and more in our Understanding the CRM Objects guide. For a more detailed look at HubSpot record types, you can use our Guide to Records.

Example use case: The tickets endpoints can be used to import ticket information from an external ticketing system into HubSpot. Providing this information to your marketing and sales teams helps prevent potentially insensitive outreach while a support case is open.


Learn about how HubSpot deduplicates ticket records here.

Ticket properties

Ticket details are stored in default and custom properties. Custom properties store specialized information and can be managed through the CRM object properties endpoints.

Required properties

When creating a new ticket, you must set the hs_pipeline_stage property.

Checking for updates (recommended)

To allow for new functionality, HubSpot will occasionally update existing default properties, and users may also change their custom properties from time to time. If your integration works with tickets, it's recommended that you use the object properties endpoints to periodically check for updates.

Associations between tickets and other objects

Tickets can be associated with contacts, companies, deals, or engagements. These associations are managed through the CRM associations endpoints.

For visual representation of how objects relate to one another in HubSpot, check out the Object Relationships section on the "Understanding the CRM" page.

Was this article helpful?
This form is used for documentation feedback only. Learn how to get help with HubSpot.