Ghost API Definition

First of all, I wanted to say that the API is extremely well documented and I really do appreciate all the time/work/effort that went into it.

I was wondering if there was any more developer centric data definition of the API model? Ideally something like swagger, or anything more formalized in a machine consumable format where.

Request type is GET,
Endpoint is /foobar/
Parameters are: q=Query, filter=type:post
Valid Response Object model looks like this and data type of each field.
Valid Errors are:

  • 501: for permission denied.
  • 404: when post already exists.

I’m just making things up but I think this captures the general idea. It would make it much easier to port or create an API wrapper for other languages if a more formalized API definition existed.

Any help is much appreciated.