Did some digging through older posts and this one discusses pulling multiple tickets:
and maybe this one that looks for specific assets:
Hopefully someone with more knowledge than me stops by to weigh in :)
Did some digging through older posts and this one discusses pulling multiple tickets:
and maybe this one that looks for specific assets:
Hopefully someone with more knowledge than me stops by to weigh in :)
This is a good place for me to start looking again. Thank you for the help!
Did some digging through older posts and this one discusses pulling multiple tickets:
and maybe this one that looks for specific assets:
Hopefully someone with more knowledge than me stops by to weigh in :)
This is a good place for me to start looking again. Thank you for the help!
I’m planning to try some stuff out with the API this summer...too many interruptions for me during the school year for me to remember something new
Good luck!
Okay, I have something that is working now!
url = https://[domain].incidentiq.com/api/v1.0/tickets
body = {
"ProductId": "{{Ticketing Product Id}}",
"Schema": "All",
"Filters": [ { "Facet": "issuecategory", "Id": "{{Issue Category Id}}" }]
}
The default seems to be 20 items but I was able to use “&$s=100” to get more records.
I am going to be playing around with this more the next few days and will add more if I discover more useful information.
Note: Ticketing ID is on the Developer Tools page, I got the issue category by running this API request:
url = https://tDOMAIN].incidentiq.com/api/v1.0/tickets/{{Ticket ID}}
and grabbed the ticket id from the URL in the ticket page in my web browser.
Thanks for sharing what worked for you!
@TLandry 5339285 orangeusd Thank you for submitting your question to our community! 
Looks like you and @AMeyer Greendale Schools figured that out together! Please let us know if you have any additional questions!
I just want to add a bit of information to this for anyone else looking into this. My current request looks like this:
url = https://[domain].incidentiq.com/api/v1.0/tickets
body = {
"ProductId": "{{Ticketing Product Id}}",
"Schema": "All",
"Filters": [
{
"Facet": "issuecategory",
"Id": "{{Issue Category Id}}"
},
{
"Facet":"ticketstate",
"Id":"00000000-0000-0000-0000-000000000000",
}
]
}
The second filter will make it return only open tickets. If you want only closed tickets, you should be able to just add “Negative”:true to the second filter.
I discovered this by setting up the filters I wanted in the ticket viewer in the browser and then using the developer console to view the API request and pulling the filter information from that. Idea from this post.
Also, I just wanted to make sure I explicitly thanked @AMeyer Greendale Schools for finding the missing link that I needed to keep exploring this.