Important: User interaction records have dependencies on students. The
system validates the
student_id against existing records in the database.
You should upload student data before uploading user interaction records to
ensure proper data validation. The item_id field must reference the correct
item type as specified by item_type.Authentication Required
This endpoint may require API key authentication via Bearer token in the Authorization header.About the Endpoint
This endpoint allows you to record and retrieve user interactions with items (TAG, OFFER, SHOP, KEYWORD).Source Field for Recommendation Feedback
Thesource field is crucial for tracking recommendation API effectiveness:
null: Normal user browsing interactions (not from recommendations)"COBI": Interactions that originated from recommendation API responses
- Track which recommendations led to user engagement
- Measure recommendation algorithm effectiveness
- Improve future recommendations based on user behavior patterns
Request Body
Type of interaction. One of: FILTER_CLICK, SHARE, PAGE_VIEW, DISCOUNT_CODE
Psuedo ID of the user
UUID of the student
One of: TAG, OFFER, SHOP
UUID of the item (TAG, OFFER, KEYWORD, or SHOP) as determined by
item_typeCity where the interaction occurred
Country where the interaction occurred
One of: ANDROID, IOS, WEB, OTHER
Event timestamp (positive integer or ISO datetime string)
Source of interaction. Set to ‘COBI’ when from recommendation API, null
otherwise
Response
The API returns a JSON response with the created interaction object on success.201 Createdon success400 Bad Requestif validation fails
Error Codes
| Status Code | Description |
|---|---|
| 201 | Interaction created successfully |
| 400 | Validation error |
| 401 | Unauthorized - Invalid API key |
| 500 | Internal server error |