Brent Sordyl's blog » api

ql.io – a SQL and JSON inspired DSL

Brent Sordyl — Wed, 07 Dec 2011 14:08:31 +0000

ql.io combines SQL, JSON, and a few procedural style constructs into a compact language. Scripts written in this language can make HTTP requests to retrieve data, perform joins between API responses, project responses, or even make requests in a loop. But note that ql.io’s scripting language is not SQL – it is SQL inspired.

(Full Story: ql.io – a SQL and JSON inspired DSL)

API design for humans – (37signals)

Brent Sordyl — Tue, 04 Oct 2011 11:48:41 +0000

Tell me more: documentation is king
Let me in: all about authentication
Underlying design: REST or something like it

(Full Story: API design for humans – (37signals))

The pros and cons of developing a complete Javascript UI

Brent Sordyl — Thu, 29 Sep 2011 18:45:35 +0000

Cons1. Javascript Frameworks are still evolving2. Developing two applications instead of one
Pros1. Well thought out and tested API2. Your JS UI code as API reference

(Full Story: The pros and cons of developing a complete Javascript UI)

The Little Manual of API Design

Brent Sordyl — Wed, 31 Aug 2011 13:55:23 +0000

Characteristics of Good API

(Full Story: The Little Manual of API Design)

Swagger: A simple, open standard for describing REST APIs with JSON

Brent Sordyl — Sun, 21 Aug 2011 12:22:24 +0000

Swagger is a specification and complete framework implementation for describing, producing, consuming, and visualizing RESTful web services. The overarching goal of Swagger is to enable client and documentation systems to update at the same pace as the server. The documentation of methods, parameters and models are tightly integrated into the server code, allowing APIs to always stay in sync. With Swagger, deploying managing, and using powerful APIs has never been easier.

(Full Story: Swagger: A simple, open standard for describing REST APIs with JSON)

The pros and cons of developing a complete Javascript UI

Brent Sordyl — Mon, 15 Aug 2011 02:00:26 +0000

Cons1. Javascript Frameworks are still evolving2. Developing two applications instead of one
Pros1. Well thought out and tested API2. Your JS UI code as API reference

(Full Story: The pros and cons of developing a complete Javascript UI)

Google’s API for APIs Makes Sense of Its 80+ Services

Brent Sordyl — Mon, 16 May 2011 19:48:52 +0000

There are other ways of describing APIs. For SOAP APIs, there are WSDL files that show methods of inputs. For REST there is WADL, but even its apparent simplicity has been too complex for some. At the very least, support for WADL has been minimal. It’s unclear whether Google has created generic enough to work for other API providers. However, it’s obviously something that Google saw the need for, at least internally.
The Google API Discovery API is one of two APIs for APIs.

(Full Story: Google’s API for APIs Makes Sense of Its 80+ Services)

An open XM to describe and distribute JSON APIs

Brent Sordyl — Tue, 19 Apr 2011 15:20:38 +0000

It may be funny we’re using XML to describe a JSON API, the reality is that this description is more like a document than a struct :) Also we needed to keep retro compatibility with our existing server library. JSON specs are on the roadmap.

(Full Story: An open XM to describe and distribute JSON APIs)

Apigee To-Go: Build, Skin, and Embed Your Own API Console

Brent Sordyl — Thu, 10 Mar 2011 20:18:22 +0000

So today we’re launching Apigee To-Go, which lets you create your own API Console, skin it with the look and feel to match your brand, and then embed it where your developers are, on your own site or portal — for free.

(Full Story: Apigee To-Go: Build, Skin, and Embed Your Own API Console)

Browse-able RESTish API Design

Brent Sordyl — Tue, 22 Feb 2011 16:34:47 +0000

We provide index pages with requests “GET /v1“, “GET /v1/client” or “GET /v1/client/366“. The index pages list all the possible sub-commands or {id} and sometimes {code} where an identifier should be substituted.

(Full Story: Browse-able RESTish API Design)