How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Open Loyalty Transactions API

Purchase transactions and points accrual.

Open Loyalty Transactions API is one of 7 APIs that Open Loyalty publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 5 operations across 4 paths, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 1.0.

Requests are made against a single base URL, https://{instance}.openloyalty.io/api.

5 operations 4 paths 1 schemas 2 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0
Base URL
https://your-instance.openloyalty.io/api
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Open Loyalty Transactions API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as X-AUTH-TOKEN (permanentToken). By default, every request must be authenticated.

  • bearerAuth — JWT obtained from POST /admin/logincheck (admin) or POST /{storeCode}/customer/logincheck (member), sent as Authorization: Bearer .
  • permanentToken — Permanent API token issued to an admin account.

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 2 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Transactions 5

Purchase transactions and points accrual.

GET
/{storeCode}/transaction
List transactions
listTransactions 3 params → 200
POST
/{storeCode}/transaction
Register a transaction
registerTransaction 1 param body → 200
POST
/{storeCode}/transaction/simulate
Simulate the points a transaction would earn
simulateTransaction 1 param body → 200
GET
/{storeCode}/transaction/{transaction}
Get a transaction
getTransaction 2 params → 200
POST
/{storeCode}/customer/transaction/customer/assign
Assign a transaction to a member
assignTransactionToCustomer 1 param body → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Transaction (3 properties). Each schema is shown below with its type and property counts.

Transaction
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

open-loyalty-transactions-api-openapi.yml Raw ↑

Other APIs Open Loyalty publishes across the network.

Open Loyalty Authorization API
Open Loyalty Earning Rules API
Open Loyalty Members API
Open Loyalty Points API
Open Loyalty Rewards API
Open Loyalty Tiers API
Where this information came from

This is an independent, third-party profile of Open Loyalty Transactions 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.