...
- To work with the XML interface and execute the SaveOrder, PayOrder, MakeRetunGoods commands, you must additionally transfer information about the LicenseInfo license
- The license is entered and generated on the licensing server (hereinafter referred to as the SLLS), while the local integration database must store in encrypted form the credentials necessary to make requests to the SL: token, active license id, sequence number of the request seqNumber
- Integration requires one of the following licenses:
Products with XML-SaaS | ProductGUID |
---|---|
R-Keeper 7 XML interface for App 12 | 655cee55-7bcd-4826-b6e0-a8ccf2017ef3 |
R-Keeper 7 XML interface for App 1 | 4458d8b1-0019-4025-8c7a-60a83ad64b66 |
Authorization
Preliminary settings:
- Enter the LS with the dealer-manager role's credentials and create a new user with limited rights
- Give this new user access (rights) to the card of the object on which it is planned to use the XML interface.
To work with requests for subscription based XML interfaces, you need the following data:
- userName — email used as a login to enter the l.ucs.ru licensing system for the created user
- password — password to enter the l.ucs.ru licensing system for the created user
- token — a unique identifier that is given to the developer company for free and is the same for all its integrations.
Credentials, i.e. the userName and password are provided by the dealer of the object on which you plan to use the XML interface. To do this, an account is created in the licensing system under an account with the dealer-manager role, which, if necessary, can be limited in rights. It is obligatory for the created account to have access to the card of the object on which it is planned to use the XML interface.
To receive a token, you need to send an email with a request to integrations@rkeeper.ru. Use the email to which the account and token will be registered.
As mentioned above, a token is given to a developer company or similar person to identify the developer when making requests. The issued token must be used for all integrations of the developer company, i.e. it is not necessary to request a new token for each new object or integration.
...