summaryrefslogtreecommitdiff
path: root/docs/api_docs.md
diff options
context:
space:
mode:
authorQMK Bot <hello@qmk.fm>2021-01-30 11:01:46 +0000
committerQMK Bot <hello@qmk.fm>2021-01-30 11:01:46 +0000
commita0e733391532490a216da044efb40451f67774f2 (patch)
tree8cc6bd43d0b70283b90cfadee1f512ef1161ff4c /docs/api_docs.md
parent6b9a7e21e953d68d6ae093c2d727f1f3ac2798c0 (diff)
parent92a787ca4cdecbbb7e2c1394d5192d5fa3dabf6d (diff)
Merge remote-tracking branch 'origin/master' into develop
Diffstat (limited to 'docs/api_docs.md')
-rw-r--r--docs/api_docs.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/api_docs.md b/docs/api_docs.md
index 28a7dd71da..5032dbc87e 100644
--- a/docs/api_docs.md
+++ b/docs/api_docs.md
@@ -28,7 +28,7 @@ As you can see the payload describes all aspects of a keyboard necessary to crea
To compile your keymap into a firmware simply POST your JSON to the `/v1/compile` endpoint. In the following example we've placed the JSON payload into a file named `json_data`.
```
-$ curl -H "Content-Type: application/json" -X POST -d "$(< json_data)" http://api.qmk.fm/v1/compile
+$ curl -H "Content-Type: application/json" -X POST -d "$(< json_data)" https://api.qmk.fm/v1/compile
{
"enqueued": true,
"job_id": "ea1514b3-bdfc-4a7b-9b5c-08752684f7f6"
@@ -40,7 +40,7 @@ $ curl -H "Content-Type: application/json" -X POST -d "$(< json_data)" http://ap
After submitting your keymap you can check the status using a simple HTTP GET call:
```
-$ curl http://api.qmk.fm/v1/compile/ea1514b3-bdfc-4a7b-9b5c-08752684f7f6
+$ curl https://api.qmk.fm/v1/compile/ea1514b3-bdfc-4a7b-9b5c-08752684f7f6
{
"created_at": "Sat, 19 Aug 2017 21:39:12 GMT",
"enqueued_at": "Sat, 19 Aug 2017 21:39:12 GMT",