Check this box if you want the app to expose an API that you or other developers/services can access to run API workflows. In addition to API workflows (which can be used for scheduled workflows), there are two other types of backend workflows: recurring events and database change trigger events.
Check this box if you want the app to expose an API that you or other developers/services can access to read or write the app data directly. When checked, select which types to expose as an API in the options that display.
GET API calls or Return Data actions can either return data with the keys being a fixed ID or use the display defined for the field in the Data Types section in the Data Tab. Choose this setting here.
Check this box if you want the app to hide the automatically generated Swagger API documentation that you or other developers/services can access. See the Swagger Specification section for more details.
If the app exposes an OAuth2 protocol, meaning users can log in to other websites using their credentials with the app, you must define the page they get redirected to once they authenticate. Select the page here.
For apps on the Professional plan and above, the Bubble app can be used as a single sign-on (SSO) provider for a Discourse forum.
This is the URL for your Discourse forum, where you want your app's end-users to be able to log into with their app username and password.
This is a token generated from Discourse.
If this checkbox is not checked, any user logging in via your app into your Discourse forum will receive Discourse's welcome email.
Checking this setting will have Discourse send email verification emails to any user who creates an account via SSO. This is generally recommended by Discourse.
If this is set, all new users created via SSO in your Discourse forum will have this image as their initial avatar.
Certain custom integrations with other web services will require the "public JSON web key" of your Bubble app. This is where you can download it.