Overview

Connect your webshop to Diller loyalty from scratch: a customer signing up or logging in on your site becomes a member in Diller, and their orders, coupons and points flow back.

Written for a backend developer. Every request is shown in full, with real field names and real response shapes.

---

Do you need a custom integration?

If your shop runs on one of these platforms, there is a ready-made plugin and you can skip almost everything here:

Platform	Use instead
WooCommerce / WordPress	Diller WooCommerce plugin
Shopify	Diller Shopify app
Magento	Diller Magento module
Shopware	Diller Shopware integration
BigCommerce	Diller BigCommerce integration
NopCommerce	Talk to your Diller contact

Read on if you are building a custom or headless storefront, or you need behaviour the plugin does not cover.

---

The mental model

There are three levels. Everything you call is scoped to a store.

flowchart TD P["Partner<br/><i>reseller / chain</i>"] --> S1["Store<br/><i>one loyalty programme</i>"] P --> S2["Store"] S1 --> D1["Department<br/><i>location or channel</i>"] S1 --> D2["Department"] S1 --> M1["Member"] S1 --> M2["Member"] M1 -.->|earns| PT["Points"] M1 -.->|holds| C["Coupons"] M1 -.->|collects| ST["Stamps"] M1 -.->|generates| T["Transactions"]

Three things follow from this that trip people up:

1. A member belongs to one store. The same person shopping at two Diller stores is two independent members. There is no global customer.
2. A department is not only a physical place. It is any origin you want to report on — Oslo, Warehouse, or Web. Most webshops create one department for online orders.
3. One set of credentials reaches one store. Read its id once from GET /api/v2.0/stores and use it in every path; any other store id is refused with 403. A chain with five stores means five credential pairs. See Authentication.

---

Vocabulary

Term	What it means
Member	A customer enrolled in a store’s loyalty programme
Department	The location or channel an action originated from
Segment	A custom profile question the store defines (interests, size, …)
Coupon	A discount the member holds; identified by a code
Stamp card	Collect n stamps, get a reward
Points	Earned on transactions, spendable on point-based coupons
Transaction	One completed order, with line items

If you see the word follower in older material, it means member.

---

What a complete integration does

Six things. Each has a chapter.

flowchart LR A["1. Get a token"] --> B["2. Read store config<br/>departments, segments"] B --> C["3. Create / match members<br/>on signup and login"] C --> D["4. Show coupons<br/>and points at checkout"] D --> E["5. Reserve coupons,<br/>post the transaction"] E --> F["6. Cancel or refund<br/>when orders change"]

Step	Chapter
1	Authentication
2	Core concepts
3	Signup and login — the important one
4–5	Checkout and coupons
5–6	Transactions

Start with the Quickstart to get a member created in about fifteen minutes, then come back and read properly.

---

Two rules to internalise now

Never call Diller from the browser

The OAuth exchange happens on your server. Your client secret, access token and store id must never reach client-side JavaScript. Your signup form posts to your own backend, which then calls us.

Always set origin.channel to "OnlineStore"

It is optional in the schema and silently falls back to POS. On a transaction, only the exact string "OnlineStore" counts as the webshop — get it wrong and every order from your shop is reported as an in-store purchase. See the callout in the quickstart.