Version 2 of our Read API

We have a new version of our Read API that provides additional data and advanced search.

I'm happy to announce that we have released a new version of our Read API that you can use to get at your Honeybadger data. This new version includes performance improvements and new endpoints. Here's a list of what has changed since V1:

  • All the endpoints that have pages now return a links element in the json that can have up to three links: self, next, and prev. Self is the URL you just fetched, and is always present. The other two give you the next and previous pages of results, and they are omitted if we know there isn’t a previous or next page. You can get a next link that ends up having no results when fetched.
  • The notices, and deploys endpoints now use the new paging params of created_after and created_before rather than page.
  • There are no longer page counts or record counts in the list responses.
  • The id type has changed in the notice response, from an integer to a UUID.
  • The team_id element in the project response has been replaced with a teams element that is an array of hashes that contain the id and name of the teams associated with the project.
  • The assignee element in the fault response has changed from a string (an email address) to an nested user object (id, name, email).
  • The environment, assignee, ignored, and resolved params are no longer supported by the faults list. These filters have been replaced by the q param, which uses the same search syntax that we use in our UI.
  • We added endpoints for sites, outages, and uptime checks. The outages and uptime checks endpoints use the created_after and created_before params for paging.
  • The authentication method has been changed -- we now depend on HTTP Basic Auth rather than passing a token in the URL params.
  • The API is now rate-limited.


When paging the notices, deploys, outages, and uptime checks endpoints, you can pass a timestamp value (seconds since the epoch) in the created_after and created_before params. This timestamp can be a float in order to specify sub-second time resolution. For example, since the notices endpoint is sorted by most recent notices first, if the last result in the first page of notices that you get back from the API has 2016-06-20T13:15:00.123456Z as the value for created_at, you can get the next page of results by including created_before=1466428500.123456 in the params.

Out with the old, in with the new

With the launch of V2, we are officially deprecating V1. We'll keep V1 around until August 1st 2016, to give people a chance to move their applications to V2. After August 1st, we'll remove the V1 endpoints. Please note that this deprecation is only for the Read API -- there are no changes being made at this time to our Collector API that the notifiers use to send errors from your apps to us.

More info

You can get all the details about interacting with the API at our documentation site. Enjoy!

What to do next:
  1. Try Honeybadger for FREE
    Honeybadger helps you find and fix errors before your users can even report them. Get set up in minutes and check monitoring off your to-do list.
    Start free trial
    Easy 5-minute setup — No credit card required
  2. Get the Honeybadger newsletter
    Each month we share news, best practices, and stories from the DevOps & monitoring community—exclusively for developers like you.
    author photo

    Benjamin Curtis

    Ben has been developing web apps and building startups since '99, and fell in love with Ruby and Rails in 2005. Before co-founding Honeybadger, he launched a couple of his own startups: Catch the Best, to help companies manage the hiring process, and RailsKits, to help Rails developers get a jump start on their projects. Ben's role at Honeybadger ranges from bare-metal to front-end... he keeps the server lights blinking happily, builds a lot of the back-end Rails code, and dips his toes into the front-end code from time to time. When he's not working, Ben likes to hang out with his wife and kids, ride his road bike, and of course hack on open source projects. :)

    More articles by Benjamin Curtis
    Stop wasting time manually checking logs for errors!

    Try the only application health monitoring tool that allows you to track application errors, uptime, and cron jobs in one simple platform.

    • Know when critical errors occur, and which customers are affected.
    • Respond instantly when your systems go down.
    • Improve the health of your systems over time.
    • Fix problems before your customers can report them!

    As developers ourselves, we hated wasting time tracking down errors—so we built the system we always wanted.

    Honeybadger tracks everything you need and nothing you don't, creating one simple solution to keep your application running and error free so you can do what you do best—release new code. Try it free and see for yourself.

    Start free trial
    Simple 5-minute setup — No credit card required

    Learn more

    "We've looked at a lot of error management systems. Honeybadger is head and shoulders above the rest and somehow gets better with every new release."
    — Michael Smith, Cofounder & CTO of YvesBlue

    Honeybadger is trusted by top companies like: