e2e guide: fix /claim response

7 years ago · 39f177b5eb
parent 857ff2573f
commit 39f177b5eb
1 changed files with 12 additions and 10 deletions
--- a/supporting-docs/guides/2016-10-18-e2e_implementation.rst
+++ b/supporting-docs/guides/2016-10-18-e2e_implementation.rst
@ -654,20 +654,22 @@ This will return a result as follows:
 .. code:: json

  {
-    "<user id>": {
-      "<device_id>": {
-        "signed_curve25519:<key_id>": {
-          "key": "<curve25519_key>",
-          "signatures": {
-            "<user_id>": {
-              "ed25519:<device_id>": "<signature>"
+    "one_time_keys": {
+      "<user id>": {
+        "<device_id>": {
+          "signed_curve25519:<key_id>": {
+            "key": "<curve25519_key>",
+            "signatures": {
+              "<user_id>": {
+                "ed25519:<device_id>": "<signature>"
+              }
            }
-          }
+          },
        },
+        ...
      },
      ...
-    },
-    ...
+    }
  }

 The client should first check the signatures on the signed key objects. As with