Upcoming API questions
Hey Gorelo Team,
we are planning our move into the Gorelo ticketing system finally. What has held us back is historical data. With the announcement of the API moving forward, it reignited the idea that we can import historical ticket records. So the question is two-pronged. How far out from the API do we think we are, and in its current planned state would it be able to touch the ticketing system?
5 Replies
I can't really give an estimate on this yet sorry. We've recently finished our SOC2 pen test and have submitted that along with other evidence for our report. During this process, we can't add to our externally accessible footprint without going through it again... so for now, that's the hold up.
Just wondering if there's any news on this? /signed API enthusiast
We’ve started on the very early work here when it’s comes to scope, auth etc.
What are your exact use cases and the endpoints you need? I’ll be able to give you a better idea of when that should be covered.
What are your exact use cases and the endpoints you need? I’ll be able to give you a better idea of when that should be covered.
this would be my wishlist:
* create/update tickets as well as add notes
* add notes to tickets
* enumerate worklog items - to QA worklog entries and adjust any that are obvious mistakes * enumerate tickets - for reporting but also for other ticket stuff as well * enumerate endpoints - for reporting mainly (especially useful if includes assigned policies) * schedule script against endpoint * add/remove tags from assets Being REST and not GraphQL would also be ideal. 😄
* enumerate worklog items - to QA worklog entries and adjust any that are obvious mistakes * enumerate tickets - for reporting but also for other ticket stuff as well * enumerate endpoints - for reporting mainly (especially useful if includes assigned policies) * schedule script against endpoint * add/remove tags from assets Being REST and not GraphQL would also be ideal. 😄
@Elliot Davis