Talon.One Loyalty API
Represents loyalty programs or concepts related to them.Loyalty programs can be _profile-based_ or _card-based_, depending on whether loyalty points are linkedto [customer profiles](https://docs.talon.one/docs/product/applications/displaying-customer-profiles) or [loyalty cards](https://docs.talon.one/docs/product/loyalty-programs/card-based/card-based-overview).See [the Product docs](https://docs.talon.one/docs/product/loyalty-programs/overview) for more information.
Talon.One Loyalty API is one of 42 APIs that Talon.One publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Loyalty. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and a getting-started guide.
This API exposes 24 operations across 24 paths, and defines 33 schemas. It is described by OpenAPI 3.2.0.
Requests are made against a single base URL, https://yourbaseurl.talon.one.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Talon.One Loyalty API declares
3 security schemes
for authenticating requests.
An API key is passed in the header as Authorization (api_key_v1).
An API key is passed in the header as Authorization (manager_auth).
An API key is passed in the header as Authorization (management_key).
api_key_v1— To authenticate with the Integration API, generate an API key in the Campaign Manager and prefix it with ApiKey-v1. To generate an API key: 1. Sign in to the C…manager_auth— This authentication scheme relies on a bearer token that you can use to access all the endpoints of the Management API. To create the token: 1. Get a bearer to…management_key— The API key authentication gives you access to the endpoints selected by the admin who created the key. Using an API key is the recommended authentication meth…
Paths & Operations 24
Across 24 paths, the API surfaces 24 operations — 16 GET, 6 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
Represents loyalty programs or concepts related to them. Loyalty programs can be profile-based or card-based, depending on whether loyalty points are linked to [customer profiles]…
Schemas 33
The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are LoyaltyProgramTransaction (21 properties), LedgerTransactionLogEntryIntegrationAPI (16 properties), LoyaltyLedgerEntry (16 properties), BaseLoyaltyProgram (15 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Talon.One 12
Other APIs Talon.One publishes across the network.
This is an independent, third-party profile of Talon.One Loyalty API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.