aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPjotr Prins2023-08-02 09:01:46 +0200
committerPjotr Prins2023-08-02 09:01:46 +0200
commit43264b1de9fd525f2aa2b624ded01041175088cb (patch)
tree91a2fd7ccfa7531d8fdb61245a7014b9c9f9e096
parent5ac80f9703083fa40c74fd3585e6611c6e74398d (diff)
downloadgn-docs-43264b1de9fd525f2aa2b624ded01041175088cb.tar.gz
GN REST API v2 conventions added - JSON tags for markdown
-rw-r--r--api/GN-REST-API-v2.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/api/GN-REST-API-v2.md b/api/GN-REST-API-v2.md
index da0bc06..b856de8 100644
--- a/api/GN-REST-API-v2.md
+++ b/api/GN-REST-API-v2.md
@@ -39,7 +39,7 @@ We may forward `api:mouse` and `api:species/Mus_musculus` (no extension) to `doc
Standard JSON data (the .json postfix) will return a minimal structure that requires the minimum amount of work to parse. Example `api:mouse.json` can result in a dictionary of:
-```js
+```json
{
"id": "Mouse",
"wikidata": "Q83310",
@@ -62,7 +62,7 @@ Standard JSON data (the .json postfix) will return a minimal structure that requ
Metadata contains further information on a JSON record, but typically not the data that is already served by above JSON record. Example for `api:mouse.meta.json`
-```
+```json
{
"api": "api:mouse.json",
"doc": "doc:mouse.html",