Read a batch of tickets by internal ID, or unique property values
A documented HubSpot Tickets operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Read a batch of tickets by internal ID, or unique property values
- POSTChanges data · Batch
api.hubapi.com/crm/v3/objects/tickets/batch/read
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which HubSpot Tickets operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other HubSpot Tickets operations
- Search for ticketsPOST · changes data
- Create a batch of ticketsPOST · changes data
- Create or update a batch of tickets by unique property valuesPOST · changes data
- Merge two ticketsPOST · changes data
- Archive a batch of tickets by IDPOST · changes data
- Update a batch of tickets by internal ID, or unique property valuesPOST · changes data
Questions
- Can HumDay read a batch of tickets by internal id, or unique property values in HubSpot Tickets?
- Yes. This operation is published in HubSpot Tickets's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my HubSpot Tickets data?
- Yes — this is a POST operation, so it changes something in HubSpot Tickets. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your HubSpot Tickets account.
Where this came from
Read from the API description HubSpot Tickets publishes themselves at api.hubspot.com/public/api/spec/v2/specs/release/22189/version/3. The description above is the provider’s own wording, not ours.