2014 was an extremely busy year at Paypal: heading up the API Design team, in an effort to API-ify over 80% of the company's capabilities. I only managed to get out three blog posts, all on [http://APIUX.com](http://apiux.com/author/jasonharmon/). As I looked at revising my strategy for sharing with the community for 2015, I had to reflect on 2014.Read More
I recently attended the API Strategy & Practices conference in San Francisco. I also attended earlier this year in New York, but this time I came as a speaker. I enjoyed the panel format in NYC so much, I decided I had to be a part of it. I wanted to bring something that I haven't heard before at API-related conferences.Read More
When it's time to build your web API, there's often a tendency to build everything around data entities. [CRUD](http://en.wikipedia.org/wiki/Create,_read,_update_and_delete)-style APIs use GET/POST/PUT/DELETE to provide the same feel as SELECT/INSERT/UPDATE/DELETE in a traditional relational database.
It's been a while since my first post in the REST Roadmap series on [RMM Level 2 / verbs / HTTP status codes](http://pragmaticapi.com/2012/12/25/rest-roadmap-upgrading-richardson-maturity-model/). I'd like to continue moving up the [RMM](http://martinfowler.com/articles/richardsonMaturityModel.html) chain, looking at Hypermedia as the Level 3, according to Martin Fowler and Leon Richardson.Read More
I've found myself explaining to lots of people what it is that I do, in working with APIs. Sure, at the office or a conference, I feel understood. However in social settings or around family, I sometimes feel like people just think I'm making this stuff up. When I try to use acronym and industry jargon filled phrases, I often just get glazed over stares and slow head nodding.
"I offer a series of integration points for mobile, web, and B2B web services consumers. Our RESTful API provides partners and developers and opportunity to monetize their application development by utilizing our marketplace platform."