{"_id":"58489b673f6eec0f00a8d010","version":{"_id":"582789aabe5c080f00a5a7fe","__v":10,"project":"568bdc1483d2061900d86cdc","createdAt":"2016-11-12T21:29:14.915Z","releaseDate":"2016-11-12T21:29:14.915Z","categories":["582789abbe5c080f00a5a7ff","582789abbe5c080f00a5a800","582789abbe5c080f00a5a801","582789abbe5c080f00a5a802","582789abbe5c080f00a5a803","582789abbe5c080f00a5a804","582789abbe5c080f00a5a805","582789abbe5c080f00a5a806","582789abbe5c080f00a5a807","582789abbe5c080f00a5a808","5827ea984ca29e0f00137a9e","583df597887db62f00644283","583df5d9c622791900e78da5","5845cd8763c11b250037967d","5845d13063c11b2500379681","5859e859e3306d1900126725","587aeb9a01cf3a0f008359eb","587c422af45e2d0f005e200d","587d84dc82f6f30f004ceee5"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"beta2","version_clean":"0.0.0","version":"0"},"project":"568bdc1483d2061900d86cdc","user":"578ef2353ac44e0e0095075c","parentDoc":null,"__v":0,"category":{"_id":"5845d13063c11b2500379681","__v":0,"version":"582789aabe5c080f00a5a7fe","project":"568bdc1483d2061900d86cdc","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-12-05T20:42:24.315Z","from_sync":false,"order":1,"slug":"platform-overview","title":"Platform Overview"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-12-07T23:29:43.923Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":8,"body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Introduction\"\n}\n[/block]\nThis API is consumed by your client application to manage end-user accounts. The authorization token provided in the header of these requests must be user authorization tokens.\n\n## Logoff a user\n\nYour client application can logoff a user. This deletes the user authorization.\n\nSee [Log Off](doc:log-off).\n\n## Verify your end-user is logged in.\n\nYour client application can verify a stored authorization token to know if a user is authenticated. \n\nSee [Status](doc:status-accounts).\n\n## Update metadata and email \n\nYour client application can update user metadata and account email address.\n\nSee [Update](doc:update-accounts).","excerpt":"For use in your client application for user management","slug":"account","type":"basic","title":"Account"}

Account

For use in your client application for user management

[block:api-header] { "type": "basic", "title": "Introduction" } [/block] This API is consumed by your client application to manage end-user accounts. The authorization token provided in the header of these requests must be user authorization tokens. ## Logoff a user Your client application can logoff a user. This deletes the user authorization. See [Log Off](doc:log-off). ## Verify your end-user is logged in. Your client application can verify a stored authorization token to know if a user is authenticated. See [Status](doc:status-accounts). ## Update metadata and email Your client application can update user metadata and account email address. See [Update](doc:update-accounts).