Okapi Okapi

api.newrelic.com · Developer tools

New Relic REST API breaking changes

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

Coming up 11

  1. /v2/alerts_channels stops working Stops workingin 281 days
  2. /v2/alerts_events stops working Stops workingin 281 days
  3. /v2/alerts_incidents stops working Stops workingin 281 days
  4. /v2/alerts_violations stops working Stops workingin 281 days
  5. /v2/applications stops working Stops workingin 281 days
  6. /v2/browser_applications stops working Stops workingin 281 days
  7. /v2/key_transactions stops working Stops workingin 281 days
  8. /v2/labels stops working Stops workingin 281 days
  9. /v2/mobile_applications stops working Stops workingin 281 days
  10. /v2/users stops working Stops workingin 281 days
  11. POST /deployments.xml stops working Stops workingin 281 days

Where Okapi reads it

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