I don’t think you need a payload either as that info is all defined within your template.
My understand of the flow is that the “Workflow Details” section of your template is a one-time “rule” that fires specifically for that template. Since you are leaving that action blank, you may have to get creative with some additional API calls that run after ticket submission. We’ve done this by pulling the TicketId from the response after submitting the ticket, from there you can set location, requestor, etc with the different endpoints.
@jclark I will definitely explore this more. Thank you! Quick question, did you find this in the API documentation? I notice I am unable to find the endpoints on the documentation that people recommend on this forum.
The former documentation that iiQ had posted a couple of years ago listed more endpoints, but was lacking a lot of information. The new documentation seems to contain more complete schemas but missing a lot of endpoints.
A lot of the endpoints I post are from referencing scripts I’ve been using for the last couple of years, or from digging into my browser trying to see what the site is doing when I perform an action. It’s not always smooth lol
@Lnguyen Our API documentation is still under review and being updated. If you ever need a specific point, you can always reach out to our support team and the Tier 2 team can get you the specifics you are looking for.