If you’re looking to programmatically create UI’s/forms to POST Ticket, our /meta endpoint does the job! The /meta endpoint allows you to programmatically pull required fields & available enum options, based on the linked account & integration. We do all the work for you so that you don’t have to.
Below are some tips for using /meta with some of the Ticketing integrations.
/meta for POST Ticket in Jira
Call /meta to know what the required fields are. For Jira, it’s
name,collection, andticket_type.
Once your customer has selected a
collection, call /meta again with “collection_id” query param. This retrieves the linked account’s available assignees & ticket types for that project, so that you can present them on your form.
Once your customer has selected the rest of the available fields, you can POST/ Ticket!
/meta for POST Ticket in ClickUp
Call /meta to know what the required fields are. For ClickUp, it’s
nameandcollectionOnce your customer selects a
collection, call /meta again & append a “collection_id” query param. This retrieves the linked account’s available lists for that project, so that you can present it on your form.
Once your customer has selected the rest of the available fields, you can POST Ticket!
/meta for POST Ticket in Trello
Call /meta to know what the required fields are. For Trello, it’s
nameandcollection.Once your customer selects a
collection, call /meta again & append “collection_id” query param. This retrieves the linked account’s available lists, assignees, & tags for that project, so that you can present it on your form.Once your customer has selected the rest of the available fields, you can POST Ticket!