Issues

GET https://992f0ac2-d8cb-4682-80df-d742797b44a9.mock.pstmn.io/issues

Gets all issues.

Request Params

KeyDatatypeRequiredDescription
qstring

HEADERS

KeyDatatypeRequiredDescription
AcceptstringIs used to set specified media type
User-Agentstring

RESPONSES

status: OK

[{"url":"https://api.github.com/repos/openreferral/specification/issues/171","id":259878292,"title":"Synchronising HSDS and HSDA documentation generation","user":"timgdavies","state":"open","comments":2,"created_at":"2017-09-22T17:04:00Z","updated_at":"2017-12-20T15:11:50Z","repository":"openreferral/specification","body":"At the moment HSDS is defined via a [datapackage.json document](https://github.com/openreferral/specification/blob/master/datapackage.json).\r\n\r\nThe [HSDA API](https://github.com/openreferral/api-specification) uses JSON Schema for definitions, manually created from HSDS.\r\n\r\nWe want to move towards a situation in which:\r\n\r\n* One of these is the Single Source of Truth (SSOT) for defining all HSDS / HSDA elements;\r\n* The other one is generated from the SSOT\r\n\r\nWe also want to ideally be able to display both the HSDA OpenAPI, and HSDS documentation in the same sphinx build. \r\n\r\nTagging @Bjwebb as this is something we could look at as part of some co-working in London in November, and our thinking about documentation generation. "},{"url":"https://api.github.com/repos/api-evangelist-tools/apis-json-annotation/issues/9","id":150580214,"title":"/api/{api_id}/buildingblocks/","user":"kinlane","state":"open","comments":0,"created_at":"2016-04-23T17:56:29Z","updated_at":"2016-04-23T17:56:29Z","repository":"api-evangelist-tools/apis-json-annotation","body":"Each API will potentially be applying some of the building blocks I track on, helping me reference who is doing what.\n"}]