In API v1 we use simple token-based authentication and authorization. This can be changed in next versions.
To access the Engine API you need the master token and additional user group’s tokens. Additional tokens you will need if you want to create several user groups with different access levels. By default, the admin group exists and the admin token is equal to the master token. Each token is a string (32 bytes length), for example
"1242ab77d1202aff87bd0b9e96e5a436". If you are our client, then you already have such a token. Otherwise, use a string
"demo" instead of a token. In this case, you will have read-only access to the
"foodmart_demo" database configuration only.
The Engine Server Endpoint
To access the Engine API you need the Engine Server Endpoint URL. For most users it is:
“1.1” is the API version number.
To respond to a user request, the server needs to have the database metadata. It is JSON-base file. The
"demo" user has access to the
"foodmart_demo" configuration (usually, another users also have access to this configuration). You need to place the database configuration file at the .Msg Cloud Processing Server (contact server administrator). You can place the finished file or the administrator will create an “empty” file for you, and you will change it using the API or the site. In this manual, all examples will use the
"foodmart_demo" database configuration. For more information about database configurations, see below.