Spoonity OffersView as markdown

Spoonity Offers

Spoonity Offers is Spoonity's promotions engine. A kiosk, POS, ordering app or partner sends it a cart. It decides which promotions and loyalty rewards apply, how they combine, and exactly how much comes off which line. Your system shows what it is given and submits it as it is. It never computes a discount itself.

Base URL: https://offers.spoonity.com

Two kinds of offer are priced together, in one pass:

Rules that hold everywhere

Surfaces

SurfacePathsWho calls itCredential
Evaluate and lifecycle/v1/evaluate, /v1/offers, /v1/redemptions/*, /v1/locks/*A kiosk, ordering app or channel backend that builds the cart itselfAPI key in X-API-Key or Authorization: Bearer
POS check/partners/pos/*A POS that sends the whole check at pay timePOS key (Authorization: Bearer)
App reward picks/partners/app/*A merchant's mobile app, so the customer can pick a reward before the tillThe customer's loyalty session key (Authorization: Bearer) plus X-Spoonity-Vendor
Admin catalog/v1/admin/*A merchant back office, or PrismAPI key
Health/readyzMonitoringNone

Which guide to read

Getting a key

Spoonity issues keys, one per merchant. There is no self-service sign-up. Ask your Spoonity account team for a key and for a test merchant to build against. Send keys only in headers: a key in a URL query string is refused, because URLs are written to request logs.

Requests and errors

{ "error": { "code": "INVALID_REQUEST", "message": "Request validation failed", "issues": [] } }

code is stable and safe to branch on. message is for people.

For AI coding assistants

These docs are also published as plain markdown, so a coding assistant can read them directly:

Give your assistant the page for your surface, and the reference, before it writes integration code. The rules above (integer cents, never compute a discount locally, fail open on 503) are the ones most often gotten wrong.