# HubSpot docs: APIs Legacy CRM Objects Tickets ## Tickets - [CRM API | Tickets](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/guide.md): A ticket represents a customer request for support. The tickets endpoints allow you to manage this data and sync it between HubSpot and other systems. - [Create](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/create-ticket.md): Create a ticket with the given properties and return a copy of the object, including the ID. Documentation and examples for creating standard tickets is provided. - [Read](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/get-ticket.md): Read an Object identified by `{ticketId}`. `{ticketId}` refers to the internal object ID by default, or optionally any unique property value as specified by the `idProperty` query param. Control what is returned via the `properties` query param. - [List](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/get-tickets.md): Read a page of tickets. Control what is returned via the `properties` query param. - [Merge two tickets](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/merge-tickets.md): Merge two tickets, combining them into one ticket record. - [Update](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/update-ticket.md): Perform a partial update of an Object identified by `{ticketId}`or optionally a unique property value as specified by the `idProperty` query param. `{ticketId}` refers to the internal object ID by default, and the `idProperty` query param refers to a property whose values are unique for the object.… - [Archive](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/delete-ticket.md): Move an Object identified by `{ticketId}` to the recycling bin. ### Batch - [Create a batch of tickets](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/batch/create-tickets.md): Create a batch of tickets. The `inputs` array can contain a `properties` object to define property values for the ticket, along with an `associations` array to define [associations](https://developers.hubspot.com/docs/guides/api/crm/associations/associations-v4) with other CRM records. - [Read a batch of tickets by internal ID, or unique property values](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/batch/get-tickets.md): Retrieve a batch of tickets by ID (`ticketId`) or unique property value (`idProperty`). - [Update a batch of tickets by internal ID, or unique property values](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/batch/update-tickets.md): Update a batch of tickets by ID (`ticketId`) or unique property value (`idProperty`). Provided property values will be overwritten. Read-only and non-existent properties will result in an error. Properties values can be cleared by passing an empty string. - [Create or update a batch of tickets by unique property values](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/batch/upsert-tickets.md): Create or update records identified by a unique property value as specified by the `idProperty` query param. `idProperty` query param refers to a property whose values are unique for the object. - [Archive a batch of tickets by ID](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/batch/delete-tickets.md): Delete a batch of tickets by ID. Deleted tickets can be restored within 90 days of deletion. Learn more about [restoring records](https://knowledge.hubspot.com/records/restore-deleted-records). ### Search - [Search for tickets](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/search/search-tickets.md): Search for tickets by filtering on properties, searching through associations, and sorting results. Learn more about [CRM search](https://developers.hubspot.com/docs/guides/api/crm/search#make-a-search-request). ### v1 - [Get a log of changes for tickets](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/v1/get-crm-objects-v1-changelog-tickets.md): Create a new ticket. The request body should be a list of ticket properties you want to set for the new ticket, with each entry being the internal name of the property to be set, and the value of that property. You must set the ticket pipeline and stage when creating a new ticket. Please see the exa… - [Get a ticket by ID](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/v1/get-crm-objects-v1-objects-tickets-id.md): Get a specific ticket by its ID. By default, the response will only include the ID and a few system fields for the ticket. You can get specific properties in the response by using the properties parameter in the URL, and that parameter can be included multiple times to get multiple properties. See t… - [Get all tickets](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/v1/get-crm-objects-v1-objects-tickets-paged.md): Get a group of tickets by their IDs. Up to 100 IDs can be included in a single request. By default, the response will only include the ID and a few system fields for the ticket. You can get specific properties in the response by using the properties parameter in the URL, and that parameter can be in… - [Create a group of tickets](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/v1/post-crm-objects-v1-objects-tickets-batch-create.md): Delete a group of existing tickets. Up to 100 tickets can be deleted in a single request. Note: This action cannot be undone. Deleted tickets cannot be updated and there is no way to restore them - [Delete a group of tickets](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/v1/post-crm-objects-v1-objects-tickets-batch-delete.md): Delete an existing ticket. Note: This action cannot be undone. Deleted tickets cannot be updated and there is no way to restore them - [Get a group of tickets by ID](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/v1/post-crm-objects-v1-objects-tickets-batch-read.md): Create a group of tickets. Up to 100 tickets can be created in a single request. The request body will be an array, with each entry being a list of ticket properties you want to set for each new ticket. You must set the ticket pipeline and stage when creating a new ticket. Please see the example for… - [Update a group of tickets](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/v1/post-crm-objects-v1-objects-tickets-batch-update.md): Update an existing ticket by its ID. The request body must be a list of properties you want to update, with each entry including the internal name of the property you want to update, and the new value for that property. See the example for details. - [Create a ticket](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/v1/post-crm-objects-v1-objects-tickets.md): Update a group of existing tickets. Up to 100 tickets can be updated in a single request. The request body will be an array, with each element containing the ID of the ticket to update and a list of properties to update for that ticket. See the examples for details. - [Update a ticket](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/v1/put-crm-objects-v1-objects-tickets-id.md): Get all tickets from a portal, up to 100 per request. By default you will only get a few system fields for any tickets in the response. If you want to get specific properties, you'll need to use the &properties= parameter in the request URL. The parameter can be included multiple times, so you can r… - [Delete a ticket](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/tickets/v1/delete-crm-objects-v1-objects-tickets-id.md): Get a list of changes to ticket objects. Returns 1000 (or fewer) changes, starting with the _least recent_ change. Returned changes are limited to the last 24 hours. Changes prior to that period will not be returned. This endpoint is designed to be polled periodically, allowing your integration to k… ## OpenAPI Specs - [crm-tickets-v3](/docs/specs/legacy/v3/crm-tickets-v3.json) - [crm-tickets-v1](/docs/specs/legacy/v1/crm-tickets-v1.json)