# Steam Signup/login API

**URL:** <https://forum.bubble.io/t/steam-signup-login-api/11319>\
**Category:** APIs\
**Created:** [March 14, 2017, 12:39am UTC](https://forum.bubble.io/t/steam-signup-login-api/11319 "2017-03-14T00:39:47Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![scottb50](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/scottb50/32/9334_2.png) [@scottb50](https://forum.bubble.io/u/scottb50)\
**Post date:** [March 28, 2017, 4:01pm UTC](https://forum.bubble.io/t/steam-signup-login-api/11319/7 "2017-03-28T16:01:29Z")

</div>

Ah, I get it. A video explaining Bubble API endpoints should be on the Bubble video to-do list, but this is a rather advanced feature. This took me a while as well, so don’t feel bad. After that, endpoints became a go-to when trying to normalize an app’s workflows.

@romanmg really tied the room together:

> [@Do when condition is true, how does it work?](http://forum.bubble.io/t/do-when-condition-is-true-how-does-it-work/7675/4):
>
> Hey @ryanck, Here’s what you need to do: Go to Settings \> API \> Turn on POST workflows Go to your page selection dropdown and at the bottom you’ll now see “API Workflows” Create a new endpoint. Name it “change\_status”. Add a key: Subscriber = User. “Subscriber” is just a label you’re giving your key and “User” is the data type for this key. We’ll use this to be able to schedule the workflow for a particular user. Create the workflow: Make a change to thing, thing to change = Subscriber…

page selection download

 ![](https://us1.discourse-cdn.com/bubble/original/2X/a/a216cd2ee93e4b358a62cd8a0bc088de8dc45b86.jpg)

---

_[View the full topic](https://forum.bubble.io/t/steam-signup-login-api/11319)._