API Upgrades and Enhancements
I will start off saying that I am by no means an API expert.
I come from the MSP space and I am seeing some big limitations that the big player have that Atera does not. That said there is a lot available here that they don't have.
To be honest, I would prefer that some of these limitations be fixed in the GUI, so that we didnt have to use the API.
For Example, being able to create a ticket natively from a script's output should be available. This is a basic requirement that I think should be added ASAP.
I am diving into automation's and I am looking at the API as a work-around for limitations in the system, but I am finding further limitations in the API. I have created a number of enhancement requests but thought I would bring them up here for further visibility and discussion.
Having a single API key is a bit scary and short sighted in my opinion. We should be able to have multiple keys for each purpose\integration. This way if we needed to remove an integration, we could just remove that specific key and not break everything else we have it tied to.
I am finding that the API has a lot of options, but seems to be lacking a number of obvious features.
First, we should be able to create a ticket tied to an agent instead of a user. This seems like a no brainer in the sense that if we are running a script against a machine and need to create a ticket, we will have the machine info available (ie. Name, Client, Serial Number,…) but not necessarily the user information.
Second, the API documentation is lacking in the sense that there are no examples for using the API in any scripting languages like PowerShell. It would be great to have a couple examples of GETs and PUTs, nothing comprehensive, but something would be nice. There are examples for using the API test page, but nothing in terms of real world usage.
Lastly, being able to manage tickets directly from a script's output is basic functionality that needs to be added. This is a non-started for a lot of MSPs and needs to be added ASAP. The whole point of automation is to be able to automate things. If a script runs and needs intervention, we are supposed to send an email to the ticketing system from PowerShell? This is a huge hole in basic functionality and needs to be added to compete at all with other vendors, and for those of us who use Atera.
Tagging @nina and @Sarah_from_Atera for visibility. I would love to talk to a product manager to give them some pointers and suggestions for frankly some basic features that would make the overall experience MUCH better and enticing for MSPs and IT Departments.
- All Topics
- 18 Getting started
- 12 Read before posting
- 6 Meet and greet
- 113 General
- 38 News and announcements
- 29 Resources
- 5 Knowledge Base
- 5 Webinars
- Shared Script Library
- 3 Pro Tips
- 16 Got an idea?
- 66 Remote Monitoring and Management
- 54 Remote Monitoring
- 12 Patch Management
- 50 Professional Services Automation
- 30 Helpdesk
- 7 Billing
- 13 Reporting
- 15 Integrations & add-ons
- 10 Integrations
- 4 Add-ons
- 45 Scripting and automations
- 34 Scripts
- 10 Automations