Skip to main content

What is the Edge API?

The Edge API is Thalamus Lite's public REST API for brand touchpoints — a website, mobile app, kiosk, point-of-sale terminal, promoter data-capture app, or partner backend. If you're building the customer-facing side of a loyalty program on Thalamus Lite, this is the only API you call. It owns all consumer identity, business rules, data, and state — your touchpoint is responsible for the UI only.

Two identities, on every call​

Every request carries up to two independent credentials:

  • Touchpoint credential (X-Touchpoint-Code + X-Touchpoint-Key) — identifies your app. Required on every single call.
  • Customer JWT (Authorization: Bearer <token>) — identifies the consumer currently using your app. Required only on calls scoped to a logged-in customer (viewing/editing their profile, verifying a channel, changing a password, logging out).

These are orthogonal by design: your app always proves who it is, and separately proves — when relevant — who the customer is. A registration or login call only needs the touchpoint credential; what you get back is a Customer JWT, which you then attach to every subsequent customer-scoped call. See Authentication for the full model.

Who should read this​

Anyone writing the client-side integration code for a touchpoint: registering and logging in consumers, letting them view/edit their own profile, and rendering registration forms with live country/subdivision data. If you're building on Thalamus Lite's BackOffice (the internal admin tool for Business staff), you want the portal-api docs instead — this is the consumer-facing surface only.

Where to go next​

  • Getting started — get a touchpoint credential and make your first call.
  • Authentication — the two-identity model in depth.
  • Errors & rate limits — the error envelope every call can return.
  • Registration — both ways to create a consumer account, end to end.
  • Login & profile — logging in and self-service profile management.
  • Reference data — country/subdivision lookups for registration forms.
  • API Reference — every method as its own page, organized in the sidebar by category: headers, body with a working JSON example, a Send API Request button, and the response (status codes + JSON) right below it.
  • Roadmap — endpoints that are reserved but not built yet, and what they return today.