# Hub status from API

**URL:** <https://community.tempest.earth/t/hub-status-from-api/6472>\
**Category:** Developers\
**Tags:** hub, rest\_api, websocket\
**Created:** [June 1, 2020, 7:14pm UTC](https://community.tempest.earth/t/hub-status-from-api/6472 "2020-06-01T19:14:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![peter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/peter/32/1365_2.png) [@peter](https://community.tempest.earth/u/peter)\
**Post date:** [June 1, 2020, 9:55pm UTC](https://community.tempest.earth/t/hub-status-from-api/6472/2 "2020-06-01T21:55:48Z")

</div>

I think (I’m guessing here) the answer to my own question lies in the fact that these details are not available to unauthorized users of the API (i.e. they can only be accessed by the station owner). In which case the Oauth2 flow is required.

> [@Cannot use websockets with Oauth2 token](https://community.tempest.earth/t/cannot-use-websockets-with-oauth2-token/5507):
>
> I used the Authorize button on the API testing interface to get a private token/key. It works fine using the REST API. However it does not work with websockets. I tried both endpoints ws and wss. I can use the demo key and all works but not the private key. Should this work or is there another way to get a private key?

@dsj sorry to badger when you are busy with Tempest, but can you comment on what progress has been made with this? Is it possible to implement Oauth2 authorization in a third party application yet?

---

_[View the full topic](https://community.tempest.earth/t/hub-status-from-api/6472)._