-
We must define if we are going to support hypermedia responses.
There are few patterns available today, I can mention:
* [json:api](http://jsonapi.org)
* [HAL - Hypertext Application Language](ht…
Cayan updated
7 years ago
-
> It’s inflexible, difficult to implement, difficult to test, with performance and implementation issues. But most importantly, any implementation of REST model is very complex.
> Now to the reader…
-
there's not much convention to our JSON responses, and @ashleygwilliams and I agree that we should implement some convention (such as [JSON API](http://jsonapi.org/))
This would be a version breaking…
-
as per slack
> Hyper-Schema is a non-validation vocabulary. A Hyper-Schema implementation would be a generic hypermedia client similar to Ketting (https://github.com/badgateway/ketting). It's not d…
-
Just wanted to get the latest definitive word on recommendations for pact in a hypermedia-rich rest api world. For reference, we generally use spring-hateoas, but I think the same sort of question wou…
-
- [ ] Documentation
- [x] SSL
- [ ] Rate limiting
- [ ] Blacklisting (or revoking access more generally)
- [x] API versioning via the `Accept` header
- [x] Resource representation negotiation (via `Ac…
-
Right now we're using some ad-hoc simple system.
http://json-schema.org/latest/json-schema-hypermedia.html
The idea is to use collections and items links for "defining" relations; but not for "res…
-
ArcGIS Open Data currently implements [JSON-API](http://jsonapi.org/) hypermedia specification for dataset searching. This supports [sites filter](https://opendata.arcgis.com/api/v2/sites?filter[url]=…
-
Referencing #49 as perhaps a concrete question, come up with some strategy for what to support and how in the hypermedia space. At first glance the space is confusing and difficult to tell what's actu…
-
We want Balanced to have the best docs possible. This issue's purpose is to track how well the [docs for 1.1](https://docs.balancedpayments.com/1.1/api/) live up to our expectations.
## What we want
…