Additions to API functionality
Hi,
First time integrator with your API, and finding it… difficult compared to other vendors.
For example - to get tickets where agents haven't logged time against them - I'd have to load all tickets in to memory and filter them client side, instead of a single query and filter on Ateras side.
Is this the recommended path, or is the API documentation missing detail that would help me out?
Thanks
Comments
-
Hey - thanks for flagging.
Please add other areas where you consider the API difficult, don't worry we take it as feedback!
As for the specific issue, I'm checking with our support and technical writer.0 -
So following up,
This is indeed the limit and workaround, I'm flagging this area with development, but there is no immediate solution here unfortunately.0
Topics
- All Topics
- 41 Getting started
- 25 Read before posting
- 8 Meet and greet
- 237 General
- 64 News and announcements
- 1 Swag
- 1 Roadmap updates
- 79 Resources
- 12 Knowledge Base
- 16 Webinars
- 1 Shared Script Library
- 2 Blog
- 19 Pro Tips
- 27 Got an idea?
- 3 Atera Academy
- 2 ActionAI
- 1 Copilot
- 140 Remote Monitoring and Management
- 84 Remote Monitoring
- 27 Patch Management
- 105 Professional Services Automation
- 64 Helpdesk
- 17 Billing
- 21 Reporting
- 36 Integrations & add-ons
- 20 Integrations
- 10 Add-ons
- 103 Scripting and automations
- 61 Scripts
- 30 Automations