Service API.
The Service API is your entry point to the GK retail platform.
- If you would like to develop brand new applications or embed GK functions in your existing app, then use the Service API
- Examples include a new consumer mobile client, or embedding our services in your existing consumer mobile app
- APIs cover functionality like security, basket management, basket calculation, promotions, loyalty, consumer management, user management, and more
- See documentation and samples for more info
Terms and Conditions
Please note, by viewing the information provided in this portal, you accept the terms and conditions below.
Your App. Our eco system. All together.
Your App.
You have the App which needs Point of Sales functionalities.
Our System.
We have a ful extensible eco system of Point of Sales Systems to integrate your content.
Swagger Documentation
POS-Services
The POS-Service is the core endpoint which is used by the flagship touch point, OmniPOS. It contains all individual operations that are orchestrated in specific macro services.
Selfscanning-API
The Selfscanning API is a simpler, stateful API. GK will maintain the basket and answer all requests with full transaction details so the client does not need to store anything.
The authentication service.
Selfscanning-Service
With the Selfscanning Service, your client maintains the basket, and GK will be used for all transactional actions.
The service depends on the others listed below.
Authentication-Service
API for Self Scanning client provided by API Gateway based on
Auth-Service API 4.5.0.
The API allows requesting a customer token for Bring Your Own Device.
Recalculate Transaction
API for Self Scanning client provided by API Gateway, based on the Pricing Service API in POS Service
Payment Service API
API for payment client provided by API Gateway, ibased on the Payment Service API 1.0.0
To run the Postman collection a user specific sandbox environment is necessary. The configuration for that can be downloaded from user page after registration.
The raw service descriptions are clearly not enough to understand the intended flows. Therefore, we have created couple of examples.
As the AppEnablement and the Service APIs are two ways to achieve similar results the examples are all in one place.
