# \[Unsupported\] Homey v2 REST API

**URL:** <https://community.homey.app/t/unsupported-homey-v2-rest-api/7268>\
**Category:** Developers\
**Created:** [January 18, 2019, 3:07pm UTC](https://community.homey.app/t/unsupported-homey-v2-rest-api/7268 "2019-01-18T15:07:04Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![lesterchan](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lesterchan/32/51_2.png) [@lesterchan](https://community.homey.app/u/lesterchan)\
**Post date:** [January 19, 2019, 12:11pm UTC](https://community.homey.app/t/unsupported-homey-v2-rest-api/7268/6 "2019-01-19T12:11:59Z")

</div>

To get the token to do auth authenticated, go to [https://developer.athom.com/](https://developer.athom.com/) and login.

After logging in, open up developer console and go to the network tab.

Look for the URL that ends with `/sessions/session/me`. Click on it and on the right should appear another panel showing the header response.

Under request headers, look for the key `authorization` and what you need is the token starting after `Bearer`

 ![Untitled-1](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/a/a9d6bf897cddbed3f622cce715d3c7570c945eaf.jpeg)

In v2, the token changed. Used to be just `<HASH>`, now it is `<UUID>:<UUID>:<HASH>` which makes it much longer.

With that, you can do a call like

```auto
curl -H "Authorization: Bearer <TOKEN>" http://<HOMEY_IP>/api/manager/devices/device

```

And you should get back a list of your devices

---

_[View the full topic](https://community.homey.app/t/unsupported-homey-v2-rest-api/7268)._