Every integration is unique but keep in mind the following points.
Which SDK do you want to use (or self-made solution)
Integration API vs Management API
Talon.One offers 2 APIs: the Integration API and the Management API. They differ in
their authentication methods and their purposes. For most use cases the Integration
API is the only API you will need.
Some promotion types like: free item campaigns, referral programs, coupon campaigns or loyalty programs require additional effect handling or some additional attributes. In such situation, ensure from the beginning which promotions you want to run through Talon.One.
Since a session is typically defined by its status: open, closed, or canceled.
When you want to create a new session, pass status: open
in the request.
During the customer's journey, the open status wont' change until the customer
reaches the final step, like the checkout step. At this point, pass status: closed.
Closing a session also feeds the session data into the campaign
analytics and a coupon in the session will be redeemed.
Important: A closed session can't be opened again.
You can set the status to canceled of open or closed sessions. This resets the
analytics data and any coupon redemption related to the session.
Sessions and profiles
A session can be connected to a profile by passing the integration id of the customer
as the value of the profileId attribute.
We highly recommend to always pass a profileId even if the customer is anonymous or
not logged in. Once an anonymous customer becomes known, replace the profileId in
the session with the new one.
Parsing the Meta-Response
Part of the customer session update response is the meta object. This object contains additional information regarding custom attribute values for all triggered campaigns and most important the reason why a coupon code was rejected.
Dealing with error responses
When a bad request is received, Talon.One returns an error code. Ensure that your
system is able to catch them or even monitor them.
Typical examples of bad requests are when the integration sends an unknown session
attribute or a wrongly formatted coupon attribute.
Talon.One API URL
We offer the possibility to move your cluster to a preferred Google cloud location.
Moving a cluster will change the API URL, such as test.talon.one/v1/ or
We suggest that you ensure your integration supports URL changes.