Delete Ticket in Apideck Issue Tracking

What this operation does

Delete Ticket

• DELETEChanges data · Ticketsunify.apideck.com/issue-tracking/collections/{collection_id}/tickets/{ticket_id}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Apideck Issue Tracking operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Apideck Issue Tracking operations

• Create TicketPOST · changes data
• Create CommentPOST · changes data
• Update TicketPATCH · changes data
• Delete CommentDELETE · changes data
• Update CommentPATCH · changes data
• List CollectionsGET · reads data
• List TicketsGET · reads data
• List CommentsGET · reads data

All 15 Apideck Issue Tracking operations

Questions

Can HumDay delete ticket in Apideck Issue Tracking?

Yes. This operation is published in Apideck Issue Tracking'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 Apideck Issue Tracking data?

Yes — this is a DELETE operation, so it changes something in Apideck Issue Tracking. 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 Apideck Issue Tracking account.

Where this came from

Read from a published API description for Apideck Issue Tracking at raw.githubusercontent.com/apideck-libraries/openapi-specs/master/issue-tracking.yml. The description above is the provider’s own wording, not ours. Last published 2023-04-19.