Okapi Okapi
Add to GitHub

api.newrelic.com · Developer toolsSubscribeShare

New Relic REST API breaking changes

The breaking changes New Relic REST API announced that Okapi tracks: 12 in all.

Do you run the New Relic REST API? Make sure your users call it right →

At a glance

API host
api.newrelic.com
Kind
Developer tools
Versions with breaking changes
v2 (11)
Next breaking change
/v2/* version retirement,
Breaking changes tracked
12 breaking changes coming up
Last updated

Coming up 12

  1. /v2/*Version retirement Stops workingin 267 days
  2. /v2/alerts_channels*Version retirement Stops workingin 267 days
  3. /v2/alerts_events*Version retirement Stops workingin 267 days
  4. /v2/alerts_incidents*Version retirement Stops workingin 267 days
  5. /v2/alerts_violations*Version retirement Stops workingin 267 days
  6. /v2/applications*Version retirement Stops workingin 267 days
  7. /v2/browser_applications*Version retirement Stops workingin 267 days
  8. /v2/key_transactions*Version retirement Stops workingin 267 days
  9. /v2/labels*Version retirement Stops workingin 267 days
  10. /v2/mobile_applications*Version retirement Stops workingin 267 days
  11. /v2/users*Version retirement Stops workingin 267 days
  12. POST /deployments.xmlEndpoint removal Stops workingin 267 days

Where Okapi reads it

Get notifications

Subscribe to New Relic REST API

Hear about each breaking change New Relic REST API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • New Relic REST API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.

Know before your API calls break.

Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.

Add to GitHub