From ca5f783b1ae451cc21f091c37358b8aa81d80ac9 Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen <paulus@home-assistant.io>
Date: Tue, 11 Sep 2018 18:10:13 +0200
Subject: [PATCH] Update auth_api.md

---
 docs/auth_api.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/auth_api.md b/docs/auth_api.md
index dc8906f4..4f3651f9 100644
--- a/docs/auth_api.md
+++ b/docs/auth_api.md
@@ -145,6 +145,7 @@ A long-lived access token is usally used for 3rd party API calls and webhook-ish
 
 Send websocket command `auth/long_lived_access_token` will create a long-lived access token for current user. Access token will not be saved in Home Assistant. User need to record the token in secure place.
 
+```json
 {
     "id": 11,
     "type": "auth/long_lived_access_token",
@@ -152,15 +153,18 @@ Send websocket command `auth/long_lived_access_token` will create a long-lived a
     "client_icon": null,
     "lifespan": 365
 }
+```
 
 Result will be a long-lived access token:
 
+```json
 {
     "id": 11,
     "type": "result",
     "success": true,
     "result": "ABCDEFGH"
 }
+```
 
 ## Making authenticated requests