APIs have existed nearly as long as software has, but in today’s microservices world, in which software is composed of small, loosely joined pieces, APIs have become the absolutely essential “glue” holding everything together. Today, New Relic is pleased to announce three notable additions to our API: new API end points for New Relic Alerts, the new “Admin User’s API key,” and a newly comprehensive API Explorer.
First, a quick note about terminology: when we use the term “APIs” in this post, we are referring to RESTful HTTPS APIs—the things you GET and POST to with JSON or, if you must, XML. We are not referring to the totally awesome, and totally different, New Relic language agent APIs.
API for New Relic Alerts Beta: Alerting for today’s modern architectures
If APIs are the glue that joins systems, notifications are the connection from those systems to the humans overseeing them. New Relic Alertsbeta has been rolling out improvements to our notifications platform for months, and today we are announcing the latest enhancement: an API for New Relic Alerts.
Many development organizations today are moving to a DevOps model in order to increase automation and velocity, and the new Alerts API is designed to enable both by providing customers with 23 new endpoints to interact with Alerts from their configuration-management tool of choice, whether it be Puppet, Chef, Ansible, or SaltStack.
If you’re using one of the technologies above, you’re likely spinning servers, containers, applications, or databases up and down on a frequent basis. We think that ensuring those new resources are covered with good alerting as each one comes online is essential to achieving 100% visibility into the health of an infrastructure, with no blind spots.
Like the programmatic automation that allows the quick creation of these new resources, an equally powerful API must be available to assign it to the right policies so the right people get notified whenever there is a service quality issue. And that is exactly what we are releasing today: an Alerts API to allow teams to automate more and continue to move faster.
Admin User’s API Key: More control and transparency
The new Admin User’s API Key adds control and transparency to New Relic API authentication. Previously, each New Relic account had only one API key (the REST API key); that key had to be shared by all admins on the account, and by all integrations that connected to that account. Now, each admin can have their own unique API key per each New Relic account. These new keys are opt-in (each admin must create their own key), deliver a “separation of privileges” versus the REST API key, include per-key and global key regeneration, and display their “date last used” for auditability.
While the REST API key will continue to exist, and will continue to authenticate API calls that mirror actions and data accessible to non-admins in New Relic’s UI, the new admin user’s API key is required for authenticating new admin-only API functionality, such as the Alerting API described above and some of the new API capabilities arriving in the coming months.
New Relic API Explorer enhancements: A one-stop API shop
The New Relic API Explorer has been enhanced with links to all New Relic APIs. This means that https://api.newrelic.com is now your one-stop shop to learn about all, not just some, of New Relic’s APIs. Most API endpoints are fully usable in the Explorer. You can select your API key, make API calls, and see the call responses in your Web browser. The API Explorer also offers CURL commands, and easy sharing of API requests by copy and pasting API Explorer URLs.
We hope you enjoy these improvements to New Relic’s API. As always, we’d love to learn what else you’d like to see in New Relic’s API. Visit our new API category https://discuss.newrelic.com/c/api in the New Relic Discussion Forum and share your thoughts with us..
Nate Heinrich contributed to this post.