Botize is the client, you are the server
The first key concept to understand about the Botize API is that it works “backwards” compared to APIs of other popular Internet services.
While it is usual that these services provide public URLs to which applications send requests to perform actions and manage data, Botize works the other way around: you, as the application developer, must host your application in any publicly accessible server. Then you register the application in Botize by simply providing a name and an entry point URL, and Botize will contact your server when appropriate (there is a mechanism that allows you to limit the rate at which Botize will access your server) to gather information about your application and to invoke their functions.
The Botize architecture allows you to bound multiple applications to one single URL. Application names are unique for the entire Botize system, therefore you can not use a name already registered by you or another user. Note however that the application name is for internal use only and will never be displayed to end users, who will see a (localizable) application title instead.
While it is usual that these services provide public URLs to which applications send requests to perform actions and manage data, Botize works the other way around: you, as the application developer, must host your application in any publicly accessible server. Then you register the application in Botize by simply providing a name and an entry point URL, and Botize will contact your server when appropriate (there is a mechanism that allows you to limit the rate at which Botize will access your server) to gather information about your application and to invoke their functions.
The Botize architecture allows you to bound multiple applications to one single URL. Application names are unique for the entire Botize system, therefore you can not use a name already registered by you or another user. Note however that the application name is for internal use only and will never be displayed to end users, who will see a (localizable) application title instead.