Before the Raygun API limited release last year, we'd been consistently receiving requests for a public API for a long time, to provide a way for our customers to access their Raygun data programmatically. We're now proud to say we're providing a public API with a range of endpoints, but it took us a lot of planning and development to get here! In this post, I'd like to take you back to the beginning of development on our big API project. Specifically, I want to walk through the pivotal decisions we made around testing when we started development on the project, and how (and why) these have paid off.