So we asked them to sit down with us to tell us a little about BlueVia. In this video, BlueVia's Dan Appelquist and Jose Valles discuss the BlueVia Platform with Jeremy Perlman of Apigee.
Tune in to learn what BlueVia is, how the platform provides access to Telefonica's assets and helps developers take apps, web services, and ideas to market.
And it's BlueVia's first birthday and they're celebrating by giving developers a...
This time, in this series about pragmatic RESTful API Design, I'll discuss authentication. There are many schools of thought - my colleagues at Apigee and I don't always agree on how to handle authentication - but overall here's my take. Let's look at how PayPal, Facebook, and Twitter handles things differently.
In the last post in this series, I talked about the top level domain (the stuff on the other side of the URL) and in this RESTful API design series so far, I've dealt with baseline, standard behaviors. This time I'll explore some of the exceptions that can happen - when clients of Web APIs can't handle all the things we've discussed. For example, sometimes clients intercept HTTP error codes, or support limited HTTP methods. What are ways to handle these situations and work within the limitations of a specific client?
In the series so far, we've talked about everything that comes after the top level domain. This time, let's explore stuff on the other side of the URL. We'll look at how Facebook, Foursquare, and Twitter handle this.
This question comes up a lot. This post talks about just one interesting way to approach it. When I first kicked off the conversation in a recent RESTful API Design webinar, I asked developers to chime in with ideas about how best to design for counts, and the conversation over on our API Craft Google group is underway. Check it out!
In the most post in this series about Pragmatic REST API design, I talked about handling responses that don't involve resources. This time, a somewhat related topic - search.
In a related post in this series about Pragmatic REST API design, I talked about partial responses and pagination. Check out the full series. This time: What's an API response that doesn't involve resources?