Users who approve your WebApp can “install” multiple WebApps.
The user can set the settings that you provided when you installed it, but they are separate for each installation.
For example, if you have a WebApp that says “Notify Slack when obniz goes offline”, you can approve it, install it with the setting of obnizID XXXX-XXX, and then install it for another obnizID, YYYY-YYY, for a total of two installations.

画像に alt 属性が指定されていません。ファイル名: webapp_install.png

Obtaining installation information from the WebApp Token

Installed app information can only be retrieved using WebApp tokens, not the OAuth token for each user.

Development of database-free web services

By using this installation, you can leave the management of OAuth and configuration information for each user in the database to obniz cloud instead of using your own server.

All your WebApp users will be able to retrieve all the information that they have set up and installed at their leisure and run your app in one place. This allows you to create a WebApp that has the following flow

  1. Use the WebApp Token at startup to obtain installation via the API
  2. Running the app according to the installation information
  3. Dynamically add and remove apps by webhooks according to user installation and uninstallation
  4. Scale-out if there are not enough server machines and reduce if there are too many

An example of a WebApp configuration using installation is available on GitHub.


You can receive a webhook when a user installs your app or makes any other changes to it.
Please see Webhook for details.