List Ticket Content Pins in Zendesk
A documented Zendesk operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
List Ticket Content Pins
- GETReads data · Ticket Content Pins
{subdomain}.{domain}.com/api/v2/ticket_content_pins
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 Zendesk operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Zendesk operations
- Record a New Skip for the Current UserPOST · changes data
- Create Ticket or Voicemail TicketPOST · changes data
- Create Ticket from TweetPOST · changes data
- Create TicketPOST · changes data
- Create Ticket FormPOST · changes data
- Create Task List TemplatePOST · changes data
- Create Task ListPOST · changes data
- Request User CreatePOST · changes data
Questions
- Can HumDay list ticket content pins in Zendesk?
- Yes. This operation is published in Zendesk's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Zendesk account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Zendesk.
- 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 Zendesk account.
Where this came from
Read from the API description Zendesk publishes themselves at developer.zendesk.com/zendesk/oas.yaml. The description above is the provider’s own wording, not ours.