API Design at Eventbrite

When Andrew Godwin joined Eventbrite, he was presented with a problem. His challenge was to take their two existing APIs, each with their respective issues, and to create an API for the modern era.

APIv1 was a bit outdated, at least 6 years old, and APIv2, in addition to being incomplete, was too specialized. Andrew's task was to create an API that wasn't stuck in the past, but also wasn't too specific. This talk discusses the steps he took to address that goal.

  • This is part 4/6 in a series on Advanced Django Patterns at Eventbrite and Lanyrd. You can find the complete series in this post.


Additional Resources from ProTech:


Published April 30, 2014