Integration

Gameball integration

Gameball is a loyalty and gamification platform. An agent can create, update, read and delete loyalty customers (with or without personal data), track orders, payments and custom events that earn points, quote what an order or event would earn, redeem, hold, award, refund and manually adjust points, generate, validate, lock, burn and release coupons, tag customers, opt them in or out, and read balances, tier and campaign progress, activities, referrals, notifications, the leaderboard and the program's cashback, redemption, referral, tier, campaign and widget settings. Point and coupon tools change real customer balances. Left out: the batch jobs (Gameball's reference and its batch guide give different routes and answers for reading a job), the customer hash route (a rotating single-use token that proves the customer is present), the coupon-engine connection settings (they hold the credentials Gameball sends to your coupon system) and six spec-only routes the reference has no page for (duplicates of the documented settings and tag routes, and an order-transactions delete whose spec text contradicts its path). Calls use API v4.0 and always send both keys, so High Security Mode accounts work; an account whose minimum allowed version is set to v4.1 refuses them. Authentication is the account's API Key (test or live) and Secret Key from Settings, Admin Settings, Account Integration, sent in the APIKey and SecretKey headers.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Gameball.Built from the 57 Gameball tools below, on the connection you add once.

What you can do with Gameball

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Transaction, 5 operations

  • activate_transactionActivate transactionPUTAgents: ask firstMakes a transaction's pending points available at once, skipping the return window. Cannot be undone with these tools.
  • count_transactionsCount transactionsGETAgents: ask firstReturns how many loyalty transactions match the filters (customer, direction, status).
  • list_transactionsList transactionsGETAgents: ask firstLists loyalty point transactions (rewards, redemptions, refunds, adjustments) with points, amounts, status, coupon and balances before and after, filtered by customer, direction or status.
  • list_transactions_with_customersList transactions with customersGETAgents: ask firstSame list as list_transactions plus each customer's name and email (personal data) and whether the customer was deleted.
  • refund_transactionRefund transactionPOSTAgents: ask firstRefunds or cancels an earlier transaction (reverseTransactionId), in full or in part (refundAmount or lineItems), and adjusts the customer's points accordingly.

Coupon, 4 operations

  • burn_couponsBurn couponsPOSTAgents: ask firstMarks a customer's coupons as used (burned), completing their redemption: pass the codes in coupons or the lockReference from validate_coupon or validate_coupons. The customer can no longer use them.
  • generate_couponGenerate couponPOSTAgents: ask firstCreates a coupon for a customer from a redemption rule (ruleId from get_redemption_settings); the rule sets the discount and how many of the customer's points it spends. Returns the code, dates, url and pin.
  • validate_couponValidate couponPOSTAgents: ask firstChecks that one coupon code can be used by a customer, optionally against a cart; with lock true it also reserves it under a lockReference that track_order can redeem (redemption.couponsLockReference).
  • validate_couponsValidate couponsPOSTAgents: ask firstChecks that several coupon codes can all be used by a customer, optionally against a cart; with lock true it also reserves them under one lockReference. All must pass: the first failure ends the call, nothing is locked.

Customer, 4 operations

  • delete_customerDelete customerDELETEAgents: ask firstDeletes a customer's profile and associated data from Gameball.
  • get_customerGet customerGETAgents: ask firstReturns a customer's profile without personal data: gameballId, attributes such as country, city, tags, spend totals and custom fields, plus referral code and links. get_customer_details adds name, email and mobile.
  • get_customer_detailsGet customer detailsGETAgents: ask firstReturns a customer's full profile including personal data (names, email, mobile, birth date, gender, city, postal code), attributes, tags, spend totals and referral code and links.
  • upsert_customerUpsert customerPOSTAgents: ask firstCreates a customer in Gameball, or updates the one with the same customerId, with contact details and attributes (names, birth date, spend totals, channel, custom fields). Returns the gameballId.

Notification, 3 operations

  • count_customer_notificationsCount customer notificationsGETAgents: ask firstReturns how many notifications a customer has, optionally only read or unread ones.
  • list_customer_notificationsList customer notificationsGETAgents: ask firstLists a customer's Gameball notifications (title, body, read status, date), optionally only read or unread ones, paged by startAfter and limit.
  • mark_customer_notifications_readMark customer notifications readPUTAgents: ask firstMarks the given notifications of a customer as read.

Points hold, 3 operations

  • get_holdGet holdGETAgents: ask firstReturns a points hold: customer, held money value and points, state and expiry date.
  • hold_pointsHold pointsPOSTAgents: ask firstReserves part of a customer's points (by ruleId, amountToHold or pointsToHold) for a later redeem_points or track_order and returns holdReference; an unused hold expires and frees the points.
  • release_holdRelease holdDELETEAgents: ask firstCancels a points hold so the held points return to the customer's available balance.

Customer activity, 2 operations

  • count_customer_activitiesCount customer activitiesGETAgents: ask firstReturns how many loyalty activities a customer has, optionally only of one activityType.
  • list_customer_activitiesList customer activitiesGETAgents: ask firstLists a customer's loyalty activity log (tier changes, campaign rewards, referrals, cashback, redemptions, refunds, expiries) with points, amounts and coupons. Includes email and phone (personal data).

Customer tag, 2 operations

  • attach_customer_tagsAttach customer tagsPOSTAgents: ask firstAdds tags to a customer. Campaigns can target customers by tag, so a tag can make campaigns available to the customer.
  • remove_customer_tagsRemove customer tagsDELETEAgents: ask firstRemoves the given tags from a customer.

Referral, 2 operations

  • count_customer_referralsCount customer referralsGETAgents: ask firstReturns how many friends a customer referred: total, active (completed) and pending.
  • list_customer_referralsList customer referralsGETAgents: ask firstLists the friends a customer referred with their id, name, email and mobile (personal data), join date and referral status (Active or Pending), paged by startAfter and limit.

Automatic coupon, 1 operation

  • apply_automatic_couponApply automatic couponPOSTAgents: ask firstApplies the account's predefined automatic coupon promotions to a cart and returns the result: isApplied, couponName, discountAmount, discountType and the discounted items.

Automation campaign, 1 operation

  • list_customer_automation_campaignsList customer automation campaignsGETAgents: ask firstLists the automation campaigns (onboarding journeys, engagement triggers, milestones) active for a customer, with their automation steps. campaignType mission (default) or all.

Campaign progress, 1 operation

  • list_customer_campaign_progressList customer campaign progressGETAgents: ask firstLists a customer's progress in each reward campaign (unlocked, completion, times achieved, streak and mission steps) with the campaign's setup. campaignType or campaignId narrow it.

Cashback, 1 operation

  • reward_cashbackReward cashbackPOSTAgents: ask firstAwards cashback points to a customer for a transaction amount under your cashback rules. Points may stay pending for the return window (configurations.returnWindow).

Cashback setting, 1 operation

  • get_cashback_settingsGet cashback settingsGETAgents: ask firstReturns the cashback earning rules: the default rule (spend threshold, points and score factors) and per-tier rules. With customerId, the rules for that customer's tier.

Coupon lock, 1 operation

  • release_couponsRelease couponsDELETEAgents: ask firstReleases a coupon lock so its coupons can be used again. Release only when the transaction is cancelled: a coupon whose lock was released then fails when used in track_order.

Customer activation, 1 operation

  • update_customer_activationUpdate customer activationPUTAgents: ask firstOpts a customer in (isActive true) or out (false) of the loyalty program, like the dashboard toggle. An opted-out customer earns and redeems nothing and leaves every campaign; past activity is kept.

Customer balance, 1 operation

  • get_customer_balanceGet customer balanceGETAgents: ask firstReturns a customer's points: total, available and pending points with their money value, the next points to expire (amount, value, date), lifetime earned points, currency and points name.

Customer coupon, 1 operation

  • list_customer_couponsList customer couponsGETAgents: ask firstLists a customer's coupons with code, type, value, validity dates, usage limits and counts, and whether each is available, expired or locked.

Event, 1 operation

  • send_eventsSend eventsPOSTAgents: ask firstRecords custom events for a customer, which your campaigns can reward with points, coupons or progress. Creates the customer when it does not exist. preview_event_rewards quotes the result first.

Event reward, 1 operation

  • preview_event_rewardsPreview event rewardsPOSTAgents: ask firstQuotes the points and coupons a customer would earn if the given events fired now, awarding nothing and using no campaign budget. The customer must already exist and be active.

Leaderboard, 1 operation

  • get_leaderboardGet leaderboardGETAgents: ask firstRanks customers by score (rank, display name, progress, tier) over a date range or all time, optionally per campaign or tag; with customerId also returns that customer's rank.

Manual transaction, 1 operation

  • create_manual_transactionCreate manual transactionPOSTAgents: ask firstAdds (positive) or deducts (negative) points, or their money value, on a customer's balance by hand, with a reason and the admin username, like a dashboard adjustment.

Order, 1 operation

  • track_orderTrack orderPOSTAgents: ask firstRecords a completed order for a customer: awards its cashback points and campaign rewards and redeems the held points or coupons passed in redemption. Creates the customer when missing.

Order cashback, 1 operation

  • calculate_order_cashbackCalculate order cashbackPOSTAgents: ask firstQuotes the cashback points and score an order would earn, per line item and campaign, without awarding anything.

Order points, 1 operation

  • get_order_points_breakdownGet order points breakdownGETAgents: ask firstExplains line by line how a tracked order's points were earned: eligible items, base rate, campaign multiplier, rounding, redeemed points and used coupon codes. Read-only.

Order reward, 1 operation

  • preview_order_rewardsPreview order rewardsPOSTAgents: ask firstQuotes everything an order would earn before checkout (the cashback quote plus place_order campaign points and coupons) without awarding anything. Campaign rewards need an existing customer (customerFound).

Order transaction, 1 operation

  • list_order_transactionsList order transactionsGETAgents: ask firstLists the loyalty transactions of one tracked order (rewards, refunds, redemptions) with dates, amounts and equivalent points.

Otp, 1 operation

  • send_redemption_otpSend redemption otpPOSTAgents: ask firstSends the customer an SMS with a one-time password for a redemption or hold (by amount, points or ruleId). Works only when SMS and OTP are enabled on the account; Gameball returns no body.

Payment, 1 operation

  • track_paymentTrack paymentPOSTAgents: ask firstRecords a completed payment (bills, services) for a customer: awards its cashback points, redeems the held points or coupons in redemption, and fires the Payment Processed event for your automations.

Payment cashback, 1 operation

  • calculate_payment_cashbackCalculate payment cashbackPOSTAgents: ask firstQuotes the cashback points and score a payment would earn, per service and campaign, without awarding anything.

Points, 1 operation

  • redeem_pointsRedeem pointsPOSTAgents: ask firstSpends a customer's points as payment on a transaction (by amount, points or a holdReference) and returns the money value and points redeemed. Accounts with OTP enabled need the customer's otp.

Redemption setting, 1 operation

  • get_redemption_settingsGet redemption settingsGETAgents: ask firstReturns how points convert to money (redemptionFactor) and the redemption rules: id, points needed, rule type, coupon details. A rule id is the ruleId of generate_coupon, hold_points and send_redemption_otp.

Referral code, 1 operation

  • validate_referrer_codeValidate referrer codeGETAgents: ask firstChecks whether a referral code is valid for signing up a new customer; forCustomerId also rejects that customer's own code (self-referral). Returns isValid.

Referral setting, 1 operation

  • get_referral_settingsGet referral settingsGETAgents: ask firstReturns the referral program setup: who is rewarded (referralMethod), the event that triggers the reward, and the points, score or coupon given to the referring customer and to the referred friend.

Reward campaign, 1 operation

  • list_reward_campaignsList reward campaignsGETAgents: ask firstLists the reward campaigns with type, visibility, availability, activation dates and rewards (points, score, coupons, streak steps). customerId, productSku or collectionId narrow it to the campaigns that apply.

Social campaign, 1 operation

  • achieve_social_campaignAchieve social campaignPOSTAgents: ask firstMarks a Social Activities campaign as achieved for an existing customer and grants its reward (points or coupon). Gameball answers 202 at once and grants the reward within a few minutes; it never creates customers.

Stamps progress, 1 operation

  • get_customer_stamps_progressGet customer stamps progressGETAgents: ask firstReturns a customer's progress in one Stamps campaign: steps completed, times earned, whether they can continue, remaining tries, end date and reward.

Streak progress, 1 operation

  • get_customer_streak_progressGet customer streak progressGETAgents: ask firstReturns a customer's progress in one daily streak campaign: current and highest streak, rewards earned, ongoing reward, next milestone, last activity and badges.

Tier, 1 operation

  • list_tiersList tiersGETAgents: ask firstLists the VIP tiers in order with the progress each needs (minProgress) and the benefits each grants (points, score, coupons, custom benefits).

Tier progress, 1 operation

  • get_customer_tier_progressGet customer tier progressGETAgents: ask firstReturns a customer's current tier, the next tier and the customer's progress toward it.

Widget setting, 1 operation

  • get_widget_settingsGet widget settingsGETAgents: ask firstReturns the program's widget and display settings as Gameball sends them; its guide shows flags such as gameballEnabled, cashbackEnabled, redemptionEnabled and notificationsEnabled, with currency and programName.

Use Gameball from Claude Code, Cursor or Codex

Connect Gameball in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Gameball operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Gameball

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Gameball once

    Add your Gameball connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Gameball integration FAQ

What can you do with the Gameball integration?

LiveContext exposes 57 operations on Gameball, covering transaction, coupon, customer and notification.

Popular integrations

Browse the whole catalog