> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://fiftytwo-demo.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://fiftytwo-demo.ferndocs.com/_mcp/server.

# 52ViKING Developer Platform

> Build on the retail platform behind the Nordics' busiest checkouts. Seven REST APIs for master data, pricing, transactions, and orders.

52ViKING platform · 7 REST APIs

Retail that runs *anywhere* you sell.

52ViKING powers the till, the app, the self-checkout, and the webshop from
one set of rules, across 4,700 stores in seven countries. These APIs give
you the same engine: master data in, prices out, transactions streamed
back.

[Start building →](/docs/introduction)

[Browse the APIs](/api/master-data/overview)

Trusted at the checkout by

![Salling Group](/_fern-files/_img/0153eb8de5c173bac27c48a7e51e9c19fdc4feda1a232a0fd9a08cd55d80e825.webp)![Netto](/_fern-files/_img/243fc8f26576f11d692c24a6aec1fa90069ba9696e5f369afd9e789e8689fa66.webp)![Bilka](/_fern-files/_img/b166d98e8645c7fd06cf6318cb3126dbe191a6760f810eaf5ae7934634e3864b.webp)![føtex](/_fern-files/_img/ed30639ae87c23c9bb6c876468ffdfcd593abfe61204007579dad4d21323270b.webp)![Matas](/_fern-files/_img/0c165ea19e9d07e0eb4ead37a0b941c433133dd0347116b01ee41c15277990fe.webp)![BAUHAUS](/_fern-files/_img/452cb3cdc93a99297ce1621438117d3f6fd9ead6bcfc23c8614f41f52574c15a.webp)![Starbucks](/_fern-files/_img/23777f08a2ca287294f2df34716f1b8fb563d14301f12a392d68545f8d0f7632.webp)![Europris](/_fern-files/_img/6248836a6bcc7402379da25c638c0aa807a2a4e91f500a5ab68bb305150d5156.webp)![MENY](/_fern-files/_img/5bb93f71c6573909ea41125d4b42dbcff8155046ec1d018f6ef8397f37e4086f.webp)![SPAR](/_fern-files/_img/d1f1cf07f6681f270b8fbec7e7a98ac7f48de0324bc41db95ac44ddad5e39128.webp)![Flügger](/_fern-files/_img/2d8607ff6c42a4cfae1b79c31fe17a3efdc7dea2b2d2d20a3ed8013f1af47160.webp)![BR](/_fern-files/_img/974bb8d3fa06fb350731a1ef70724368d91df325e9d2f451f2b0ab03d21a5459.webp)![Dagrofa](/_fern-files/_img/c977c86c4641f45d3e66d47fa4fe4edbdcb60340dd34925e07d75f7ce26d0549.webp)

Seven APIs, one commerce engine

Every endpoint speaks the same domain of articles, discount groups,
campaigns, tills, and receipts, so a rule you set once applies wherever
the customer checks out.

[◧](/api/master-data/overview)

### Master Data

Articles, article groups, campaigns, discount groups, coupons, customers, operators, and store groups. The catalogue of record.

101 endpoints async writes

[∑](/api/basket/overview)

### Basket

Price a basket exactly the way a till would. Every campaign, ladder, mix discount, and Buy side / Get side rule applies identically.

XML or JSON stateless

[≋](/api/transactions/overview)

### Transaction POS Log

Rich transaction events pushed to you as they happen, instead of polling for yesterday's receipts.

event-driven replaces Receipt API

[⇄](/api/register-sale/overview)

### Register Sale

Import finished sales from a webshop or self-checkout into ViKING POS, so returns work in any physical store.

OpenAPI 3.1 Bearer JWT

[◇](/api/order/overview)

### Order

Order requests behind click & collect, ship-from-store, and endless-aisle flows.

7 operations

[⚿](/api/auth/overview)

### Auth

Exchange a client secret for the access token every other 52 Cloud API call requires.

auth.fiftytwo.com

[✳](/help/overview)

### Help center

Concepts, Store Management, POS, MPOS, and POS Designer — the product documentation, searchable alongside the APIs.

92 topics 10 sections

**3M+**&#x54;ransactions through ViKING every day **4,700+**&#x53;tores running the platform **16,000**Checkout terminals **33M**Consumers handed a receipt each week

One site, not two

The help center and the API reference, finally together

A developer wiring up discount groups needs the endpoint schema
*and* the topic explaining what Buy side / Get side means.
Those have always lived on separate domains. Here they're one
searchable corpus, with one `llms.txt` for coding agents.

* **One search, both halves.** Look up "discount group" and get the
  endpoint that writes it and the topic that explains it, in the same
  results.
* **Concepts next to the calls.** Discount groups, campaigns, and
  transaction types sit one click from the endpoints that write them.
* **Readable by agents.** Every product exposes its own
  `llms.txt`, so a coding assistant can pull just the
  Basket API or just the help center.

**Platform concepts**12

Discount types→

Payment methods→

**Store Management**39

Discount groups→

Buy side / Get side→

**ViKING POS**14

**MPOS · Emergency POS · Designer**19

**52LEASING · 52eSELLER**2

Start where you are

Four integrations cover most of what teams build on 52ViKING.

#### [Sync a product catalog](/docs/guides/sync-catalog)

Push articles, groups, and prices into 52ViKING and poll for the
asynchronous result.

#### [Price a basket from a webshop](/docs/guides/price-a-basket)

Get till-identical totals online, including campaigns and Buy side / Get
side rules.

#### [Import webshop sales into the POS](/docs/guides/import-sales)

Register finished online sales so customers can return goods in any
store.

#### [Consume transaction events](/docs/guides/transaction-events)

Receive pushed POS log events instead of polling, and handle replays
safely.