# Create flow over API

**URL:** <https://community.homey.app/t/create-flow-over-api/19199>\
**Category:** Developers\
**Created:** [October 13, 2019, 6:36am UTC](https://community.homey.app/t/create-flow-over-api/19199 "2019-10-13T06:36:44Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![homeyuser](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/homeyuser/32/16390_2.png) [@homeyuser](https://community.homey.app/u/homeyuser)\
**Post date:** [October 13, 2019, 12:19pm UTC](https://community.homey.app/t/create-flow-over-api/19199/3 "2019-10-13T12:19:36Z")

</div>

Hi and thanks for your reply!  
The authentication is not the problem. I’ve autenticated successfully using the bearer token in the v2 format as described in [this post](https://community.homey.app/t/unsupported-homey-v2-rest-api/7268/6).  
I am simply not sure where to send my (I suppose) PUT request, to what endpoint. So i can for example perform a GET request to get a list of all the devices here:  
  
http://\<HOMEY\_IP\>/api/manager/devices/device/   
and get a list of all flows here:  
http://\<HOMEY\_IP\>/api/manager/flow/flow/.   
This is straightforward. But I am not sure how to craft a createFlow action over pure HTTP since http://\<HOMEY\_IP\>/api/manager/flow/createFlow/ for example gives me a 404. When I found out how to do so, I’ll just make a copy of my current flows to ensure I have all the triggers etc in place before starting to substitute parts and make it more dynamic.

Yes, I have successfully created flows using the playground.

Oh, and happy birthday @Dijker! 🙂

---

_[View the full topic](https://community.homey.app/t/create-flow-over-api/19199)._