This API is designed to provide POS, online ordering, and kiosk providers the ability to integrate Thanx Loyalty into their ordering systems - reward redemption & loyalty points accrual. This API provides a way to retrieve a user’s rewards and apply discounts to their basket. An online ordering platform with a shared restaurant customer can integrate with these APIs to allow Thanx users to both use their discounts while placing digital orders and accrue points progress while doing so.
  • The GET /account endpoint provides a user’s available rewards.
  • The POST /baskets endpoint computes a discount and marks rewards or points product as used in the Thanx system.
    • Ordering partners are expected to apply the discounts returned by this endpoint if a reward or points product was specified.
    • Finalized baskets automatically accrue points for the authenticated user.

​
Certification

Once your integration has been built and developed against the sandbox environment, please reach out to developer.support@thanx.com go through a lightweight but mandatory certification process. For basic integration use-cases, certification is quick and normally takes no more than a few days depending on the scope of integration. This process is mainly designed to ensure the integration is working as intended without risking any negative impact on live customers (merchant or consumer). The certification process will start with a video call with members of our developer support team. On the call, your team will demo the integration and all the supported use-cases. After the demo of all support use-cases, our team will validate the following:
  • Interactions
    1. authentication
    2. loyalty lookup, such as reward or points product
    3. order submission with or without loyalty redemption
    4. walk through examples of all supported loyalty types:
      • reward redemption workflow:
        • amount off rewards
        • item-based rewards
      • points redemption workflow:
        • amount off points products
        • item-based points products
    5. error message handling
  • API
    1. requests must include all required headers
    2. requests must not be unnecessarily duplicated
    3. error messages should be displayed to the user
    4. requests should only be issued on a reasonable frequency and in response to end-user interactions (e.g. Don’t rapidly poll the API for changes)
Each net new integration use-case should be re-certified as new use-cases will very likely require different scoping. Launching new merchants on certified integration use-cases does not require re-certification.