Yahapi is a basic hypermedia-enabled REST convention. Its primary goal is to simplify API decisions you might need to make while building backend API's.
Yahapi guides your API design to:
- … link resources to each other;
- … embed different resource types within your JSON response;
- … provide a single unified error format for you API;
- … promote you to add references to your API documentation in your JSON response;
- … define how to return partial results;
- … sort and paginate collections.
In the end Yahapi is just a list of preferences that make your API look nice, simple and consistent.
Assume the following response:
GET /orders/43983
{
"order_id": 43983,
"created": "2014-08-05 16:22:16",
"modified": "2015-05-22 13:45:20",
"user_id": "914",
"items": [
{
"order_item_id": "912332",
"product_id": "EZ-21562",
"amount": 3
},
{
"order_item_id": "912333",
"product_id": "AF-49841",
"amount": 1
}
]
}
The same resource in Yahapi might look something like this:
GET /orders/43983
{
"id": 43983,
"created": "2014-08-05T16:22:16Z",
"modified": "2015-05-22T13:45:20Z",
"user_id": "914",
"type": "order",
"order_items": [
{
"id": "912332",
"product_id": "EZ-21562",
"amount": 3,
"links": {
"self": { "href": "/orders/43983/items/912332" },
"product": { "href": "/products/EZ-21562" }
}
},
{
"id": "912333",
"product_id": "AF-49841",
"amount": 1,
"links": {
"self": { "href": "/orders/43983/items/912333" },
"product": { "href": "/products/AF-49841" }
}
}
],
"links": {
"self": { "href": "/orders/43983" },
"user": { "href": "/users/914" },
"items": { "href": "/orders/43983/items" }
},
"meta": {
"retrieved_on": "2014-08-06T11:38:24.162Z"
}
}
Yahapi uses four reserved top-level keywords: id, type, links and meta.
- id: the unique url parameter identifying the resource.
- type: identifies the object as a resource (e.g.
order) or as an embedded resource (e.g.orderItem) and tells the client how to process that resource. - links: is a collection of url's related to the resource that may be of interest to the client.
- meta: contains any meta-information about the resource such as pagination.
In a worldfullofhypermediatypes why choose Yahapi?
In our experience no current Hypermedia type is a practical standard. That is, none of them make your life easier. Most are either too much focused on a specific use case or lack features to fully drive your API design. One hypermedia type that comes close to being a full style- and hypermedia-guide is JSON API. While JSON API is quite beautiful it requires an advanced server and smart client to make fully use of.
Yahapi is designed to keep things simple. Yahapi adds hypermedia controls with limited modifications to the "naive" JSON REST design, promoting readability and simplicity.
To this end Yahapi provides a list of guidelines for pagination, sorting, partial results and error formats; these guidelines should save you time searching for best practices and make for a more consistent API.
Yahapi makes your clients have more fun integrating your service.
Yahapi is a work in progress, if you feel like contributing open up an issue to start off a discussion or create a Pull Request with your suggested changes.