API Key Manager / API Security / Expanding capabilities / OpenAPI compliance
Ability to create and manage multiple API keys per account.
Detailed API key management with read, write, and delete permissions.
Restrict access by IP address.
Set expiration dates for API keys to enforce temporary access.
Updated, OpenAPI-compliant documentation for easier integration.
Enhanced security and reduced risk of misuse.
Flexible access control with multiple API keys for different integrations.
Clear, modern, and standardized documentation for IT technicians..
Easier management and auditing of API keys.
abigael abigael
shared this idea
Hi,
Great news! Your idea has been approved and is planned for implementation.
We appreciate your contribution and will keep you informed about the progress and expected release date, as well as here in the portal.
[For major features only–] You can also follow this in our Pubic Roadmap.
Best regards,
The Atera Team
-
Stric Support
commented
Currently, it is possible to create a new customer using the API. From here, I can even create folders under the customer. I can even assign a threshold to a folder.
The only thing I am missing, is the ability to set Patch automation profiles to the folders.
This means that adding a customer is still a 2 fold job. Running a script and manually adding the correct patch automation profiles.
-
Rhys Price
commented
We use the API to produce custom reports for customers showing the agent details they find important. It would be useful to also be able to include site name for customers with multiple sites, we typically use folders to manage this but when getting agent info from API we can only see a folder ID and there doesn't seem to be a way to get the folder name via API to add this to our reporting. Would it be possible for the get agent API to include folder name or alternatively could there be a way to get the folder name from the folder ID with a separate API?
-
Lars Elgaard
commented
The ability to create contracts on specific customers. During a on-boarding automation process, it would be great to be able to create contracts on a customer. Also the ability to set the default contract.
-
abigael abigael
commented
Ability to monitor API. Seeing if they are up or down, or overloaded.
-
Stavros Patiniotis
commented
Ability to pull reports via api. Ideally being able to limit at customer or device level or otherwise allow a complete dump.
-
Rajesh Gupta
commented
We need a feature of API – getting a list of installed applications per agent.
This would be the same data that we would get from regular reports, but would be visible at the agent level via their REST API.
-
Matt Hardwick
commented
*We need the option to create per app/per customer API keys.*
There are talks here of having separate read/write API keys but it needs to go one further. We need the option to create multiple keys and define the scope, limiting the features available and/or per customer. Currently keys are transferred in the to customer devices when used in a script, and thus pose a security risk.
-
Matt Hardwick
commented
Huge security risk to only have a singly read/write API key - I see there are suggestions for separate read/write one but realistically we should be generating keys per app and have the option to limit the scope to specific features or customers.
The API key gets transferred in the clear on PowerShell scripts to a customer device - so there really needs to be some improvements in this area.
-
Authentix Support
commented
Currently you can open the portal, go to agent, click Edit, and change the name of the "Agent" for an endpoint.
Please allow the AgentName to be updated via API as well. Same permission and process just programmatically.
-
Jogchum van Bochove
commented
We are managing our SLA's in other software than Atera. It would be great to use the API to sync contracts.