# \[App\]\[Pro\] Local API

**URL:** <https://community.homey.app/t/app-pro-local-api/70840>\
**Category:** Apps\
**Tags:** app, flow, homey-pro\
**Created:** [October 19, 2022, 3:50pm UTC](https://community.homey.app/t/app-pro-local-api/70840 "2022-10-19T15:50:01Z")\
**Posts on this page:** 1\
**Page:** 5

<div class="post-metadata">

**Author:** ![Fredrik\_Stafberg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fredrik_stafberg/32/79116_2.png) [@Fredrik\_Stafberg](https://community.homey.app/u/Fredrik_Stafberg)\
**Post date:** [October 16, 2024, 1:27pm UTC](https://community.homey.app/t/app-pro-local-api/70840/83 "2024-10-16T13:27:09Z")

</div>

Hi,

I am using this with Bitfocus Companion [https://bitfocus.io](https://bitfocus.io) to control lights and monitors through Homey.  
I would like to pass data to homey, and would therefore like to see a split in the call like this:

[http://my.homey.ip/LocalAPI?a=1&b=2](http://my.homey.ip/LocalAPI?a=1&b=2)  
First part before the ? is the endpoint,  
and after the ? is the payload.  
Sending this payload on to next card as a “result” would be a great addition 🙂

I see the value of being able to reuse same endpoint for multiple calls Ex:  
[http://my.homey.ip/LocalAPI?temperature=indoor](http://my.homey.ip/LocalAPI?temperature=indoor)  
[http://my.homey.ip/LocalAPI?room=office&light=ceiling&colour=50](http://my.homey.ip/LocalAPI?room=office&light=ceiling&colour=50)

Thank you for great work!  
/Fredrik

[Previous page](https://community.homey.app/t/app-pro-local-api/70840.md?page=4)