Skip to navigation

About the Register Sale API

Import finished sales from webshops and self-checkout into ViKING POS.

View as Markdown

The Register Sale API lets external systems such as webshops and self-checkout solutions import finished sales into ViKING POS. Once a sale exists in the estate, a customer can return the goods in a physical store.

This is for sales already completed and paid for elsewhere. To price a basket before payment, use Basket API.

Endpoints

POST /v1/sale submit a sale, receive a correlation ID
GET /v1/sale/{correlationId} check processing status

Base URL: https://api.fiftytwo.com/register-sale-api

Asynchronous by design

Sale processing is asynchronous. Submitting returns a correlation ID immediately; use it to poll until the sale is Processed or Failed.

A sale starts as Pending and transitions to exactly one terminal state:

StatusMeaning
PendingSubmitted, not yet processed
ProcessedImported successfully
FailedRejected. A real outcome, not a transport error

Authentication

Register Sale uses an Auth0-issued Bearer JWT, not a token from auth.fiftytwo.com like the other 52 Cloud APIs. Same header format, different issuer. Ask your FiftyTwo consultant which tenant issues yours.

Idempotency

A timed-out POST /v1/sale leaves you unsure whether the sale was accepted. Retrying blindly can import it twice, and a duplicate sale means the same goods could be returned twice. Persist the correlation ID against your own order ID before treating the submission as done.

Next