In the Swagger YAML files, response schema specs are not given. For example, for /account_name:
|
"/account_name": |
|
get: |
|
description: Get account name by ID |
|
operationId: api.explorer.get_account_name |
|
parameters: |
|
- in: query |
|
name: account_id |
|
default: 1.2.0 |
|
type: string |
|
required: true |
|
description: Account ID (1.2.X) |
|
responses: |
|
'200': |
|
description: 1 account name |
|
'500': |
|
description: Error processing parameters |
|
tags: |
|
- api |
|
- account |
In responses, it gives only description for each status code. The schema spec (https://swagger.io/docs/specification/2-0/describing-responses/) is missing.
This may not be a big issue in some use cases. However, we will not be able to use the API with some Swagger clients who rely on the schema to unmarshal JSON (like Bravado). This makes it harder for non-technical data analysis people to retrieve and make use of the API.
In the Swagger YAML files, response
schemaspecs are not given. For example, for/account_name:bitshares-explorer-api/swagger/paths_explorer.yaml
Lines 33 to 51 in 9444323
In
responses, it gives onlydescriptionfor each status code. Theschemaspec (https://swagger.io/docs/specification/2-0/describing-responses/) is missing.This may not be a big issue in some use cases. However, we will not be able to use the API with some Swagger clients who rely on the
schemato unmarshal JSON (like Bravado). This makes it harder for non-technical data analysis people to retrieve and make use of the API.