Talon.One has added role-based access to its AI-agent connection and expanded the APIs used to retrieve customer reward information. The changes were documented in the incentives platform's September 23 product release. [S01]
Users connecting an AI agent through Talon.One's MCP server can now sign in with their own account using OAuth 2.0 instead of relying on a shared API key. The company says the connected agent inherits that user's role permissions.
For an operator, this ties access to the permissions already assigned to a person in the platform. The release does not describe an independent security evaluation or make the change a guarantee against unauthorized activity.
More visibility into reward status
New and updated endpoints can return rewards that a customer has unlocked or used. Reward information can also be included when updating a customer profile or tracking an advanced event, while the administrative rewards list gains search and filtering by name, application and status.
These changes concern how another system retrieves and manages reward state. They do not establish a new gift-card denomination, merchant catalogue or consumer payout product.
Talon.One's existing platform supports generating gift-card codes with a value that pays for part or all of an order. The new access and retrieval functions sit alongside that broader incentives infrastructure. [S02]
The current specification makes reward retrieval configurable from one to 1,000 records per page, with 1,000 also the default. The endpoint includes shared rewards unlocked through a linked loyalty card and is marked experimental. These bounds explain how an integration pages through reward state; they do not count users, establish response speed or limit a customer to 1,000 rewards. [S03]
Permitted customer-reward response page size
Published parameter bounds for the current customer-rewards endpoint.
reward records per page
Tap or hover for details. All values are also available in the data table.
Source
Configuration limits, not actual record counts, throughput or latency. Endpoint marked experimental; shared loyalty-card rewards can be included, not gift-card balances alone.
Show data tableHide data table
| Category | Documented allocation or limit |
|---|---|
| Minimum configured page size | 1 reward records per page |
| Maximum and default page size | 1,000 reward records per page |
Availability and operating limits
The update also adds an API for creating campaigns. A new structured ruleset endpoint is labeled beta, while a redesigned campaign overview is in closed beta. Those qualifications limit any claim that every feature in the release is generally available.
Other changes cover loyalty attributes, balance exports and coupon limits. One documentation discrepancy remains: the release announces a 10,000,000 redemption limit for random and universal coupon codes, while the current API schema still sets CouponConstraints.usageLimit to a maximum of 999,999. These statements do not establish a verified before-and-after limit or which bound a particular deployment enforces. Together, the release gives programme operators additional tools to connect incentive decisions, customer records and administration. [S01] [S03]
Separate existing gift-card generation rules illustrate another operating distinction. The guide permits up to 20,000 gift cards immediately and up to 5,000,000 in one request; requests above 20,000 use asynchronous generation and an email notification, with the guide allowing up to an hour. Those are documented issuance limits, not the coupon redemption cap or measured generation speed. [S02]
Documented gift-card generation limits
Published thresholds in the gift-card generation guide.
gift cards per generation request
Tap or hover for details. All values are also available in the data table.
Source
The larger request ceiling includes the immediate range; the bars are not additive, actual issuance, a historical increase or measured throughput. These issuance rules are separate from coupon redemption limits.
Show data tableHide data table
| Category | Documented allocation or limit |
|---|---|
| Immediate-generation ceiling | 20,000 gift cards per generation request |
| Maximum per request, asynchronous above 20,000 | 5,000,000 gift cards per generation request |
Talon.One did not disclose pricing changes or adoption figures for the new functions. Its refreshed branding also appears in the notes, but the previously completed ownership change is separate from this September product update.
In this article
Daniel Brooks
Daniel Brooks covers payment networks, financial technology, payment security, gift card fraud and PCI DSS for Gift Card News.