tracking
Authorization
bearerAuth In: header
Request Body
application/json
AiFi store id
ISO formatted creation time of the event, that caused this webhook to be sent
date-timeISO formatted time, in which this webhook was sent
date-timeIdentifier of the Shopper. It can be null when AiFi will not be able to match Shopper
External unique event id that comes to AiFi systems from outside system
Response Body
curl -X POST "https://oasis-api.public.sandbox.oasis.aifi.com/api/push/tracking" \ -H "Content-Type: application/json" \ -d '{ "storeId": 0, "store": { "oasisApiStoreId": 0, "aifiUniqueStoreId": "string" }, "timeOfOrigin": "2019-08-24T14:15:22Z", "timeOfIssue": "2019-08-24T14:15:22Z", "shopperId": "string", "uniqueEventId": "string" }'How is this guide?
possible fraudulent shoppers/strange behaviors are identified POST
AiFi system shall call this webhook when a possible fraudulent shoppers/strange behaviors are identified. This webhook is intended to be only informative: no response is parsed and no action is taken regardless of the response.
customer entered a store POST
AiFi system shall call this webhook when a customer entered a store. This webhook is intended to be only informative: no response is parsed and no action is taken regardless of the response. **IMPORTANT NOTE**: This event is going to be triggered for **every person from the group** that entered on the account of the provided customer. As an example for a group of 2 people that enter together on a single app you get the exact same push notification twice with ```customer``` field being the person that app was registered for after each person has entered the store. **Note**: as an integrator the URL you specify for transitions webhooks will be re-used for all transitions actions. For example if you specify "http://example-retailer-api.com/webhook" then "http://example-retailer-api.com/webhook/entered" will be called in this case.