aboutsummaryrefslogtreecommitdiff
path: root/docs/api_docs.md
diff options
context:
space:
mode:
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 28a7dd71d..5032dbc87 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
28To 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`. 28To 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`.
29 29
30``` 30```
31$ curl -H "Content-Type: application/json" -X POST -d "$(< json_data)" http://api.qmk.fm/v1/compile 31$ curl -H "Content-Type: application/json" -X POST -d "$(< json_data)" https://api.qmk.fm/v1/compile
32{ 32{
33 "enqueued": true, 33 "enqueued": true,
34 "job_id": "ea1514b3-bdfc-4a7b-9b5c-08752684f7f6" 34 "job_id": "ea1514b3-bdfc-4a7b-9b5c-08752684f7f6"
@@ -40,7 +40,7 @@ $ curl -H "Content-Type: application/json" -X POST -d "$(< json_data)" http://ap
40After submitting your keymap you can check the status using a simple HTTP GET call: 40After submitting your keymap you can check the status using a simple HTTP GET call:
41 41
42``` 42```
43$ curl http://api.qmk.fm/v1/compile/ea1514b3-bdfc-4a7b-9b5c-08752684f7f6 43$ curl https://api.qmk.fm/v1/compile/ea1514b3-bdfc-4a7b-9b5c-08752684f7f6
44{ 44{
45 "created_at": "Sat, 19 Aug 2017 21:39:12 GMT", 45 "created_at": "Sat, 19 Aug 2017 21:39:12 GMT",
46 "enqueued_at": "Sat, 19 Aug 2017 21:39:12 GMT", 46 "enqueued_at": "Sat, 19 Aug 2017 21:39:12 GMT",