Cumulus number.
Match pattern:^\d{13}$
>= 13 characters<= 13 characters
Example:2099123456789
GTIN (EAN) of Coupon. Its a string as GTINs often are longer than what integers can represent.
Match pattern:^\d+$
Only non-redeem Coupons can be deactivated. It’s okay to deactivate an already inactive Coupon.
Note: The parameters can be sent as query parameters in the URL or as application/x-www-form-urlencoded in the request body (or any combination, it just doesn’t matter.)
Cumulus number.
Match pattern:^\d{13}$
>= 13 characters<= 13 characters
Example:2099123456789
GTIN (EAN) of Coupon. Its a string as GTINs often are longer than what integers can represent.
Match pattern:^\d+$
Successfully deactivated
Redeem a Coupon i.e. use it in a purchase.
Note: The parameters can be sent as query parameters in the URL or as application/x-www-form-urlencoded in the request body (or any combination, it just doesn’t matter.)
The Migros internal costcenter number (Kostenstelle) to be billed. This is necessary especially for charge and reddeem.
>= 1000000<= 9999999
You probably should not send this value at all unless this is some kind of offline request for some internal transaction that happened in the past. It’s whole purpose is for logging and correlating different transactions but this is better done via transaction_id.
Format is Y-m-d\TH:i:s; Default is the time this call arrives at Reti.
Match pattern:\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}
Example:2023-08-17T14:03:05
Only ‘Kassen’ must use this field and send the Kassen-Nr/Terminal.
All other clients must leave this fields blank.
<= 999
Example:78
Transaktions-Nummer; gruppiert z.B. mehrere ReTi-Calls für denselben Kunden.
>= 3 characters<= 32 characters
Example:jdfjhamnasdl239msnsds34
Die Unique Request-Id muss innerhalb einer konfigurierten Zeitspanne (aktuell 300s) einmalig für das aktuelle Ereignis sein (z.B. Kauftransaktion X für Kunde Y und Coupon Z). Anhand dieser ID beurteilt ReTi, ob ein Charge bereits erfolgt ist (Offline-Buchungen, Mehrfach-Aufrufe usw.).
>= 3 characters<= 32 characters
Example:lksdfji3dmcns834la
Channel of the coupon; 1 = paper, 2 = digital, 3 = both (e.g. Bonus-Coupon). Usually when making a charge through the M-API you’ll want to use 2.
Allowed values:123
Example:2
Coupon type; 1 = transferable, 2 = personal/not transferable, 3 = Earlybird. Bonus coupons are personal. Falls der Checkcode fehlt, wird bei Bonus-Coupons (8888*) check_code==2 angenommen; bei allen anderen werden die vorhandenen Stammdaten berücksichtigt.
Allowed values:123
Quantity of coupons to assign. By default 1. More than one is not really a use-case.
>= 1<= 99
Cumulus number.
Match pattern:^\d{13}$
>= 13 characters<= 13 characters
Example:2099123456789
GTIN (EAN) of Coupon. Its a string as GTINs often are longer than what integers can represent.
Match pattern:^\d+$
Charge successful
This endpoint allows to match a set of Product-IDs against the current Coupons attributed to a customer.
Only Rabattcoupons and Bonuscoupons in the state Available or Activated are matched. Partnercoupons, Preview Coupons and Coupons that have been Redeemed already are not returned.
Like in the other endpoints working with Product IDs this endpoint also operates with the IDs of actual, buyable products as well as the corresponding “Sammler” products.
The response contains a map of Coupon GTINs that are applicable to at least one of the given products. The map entries contain the UserCoupon data, whether this Coupon matches the whole sortiment and the actual IDs matched.
Unlike the product matching endpoints on unpersonalised coupons this endpoint only provides the POST variant.
Cumulus number.
Match pattern:^\d{13}$
>= 13 characters<= 13 characters
Example:2099123456789
Product IDs to check, provided as (multiple) id form parameter(s).
Map of GTINs to coupon and product data
This endpoint returns aggregate summary data of a users Coupons and UCBs.
Note that a single ‘Coupons’ can be attributed to a customer several times in which case the Quantity field is larger than 1. The dirac… fields in the response honour Quantity and count such Coupons multiple times while the coupons… field(s) count Coupon types ignoring their Quantity.
Cumulus number.
Match pattern:^\d{13}$
>= 13 characters<= 13 characters
Example:2099123456789
Summary data.
Aggregate statistics about Coupons and UCBs of a user.
Number of activated Coupons (ignoring Quantity).
Example:3
Total number of activated Coupons (counting Quantity).
Example:4
Number of non-redeem Coupons (ignoring Quantity)
Example:7
Sum of all activated UCBs in CHF
Example:30
Sum of all non-redeemed UCBs in CHF.
Example:75
This endpoint returns the set of all UCBs (aka “Blaue Bons” aka “Cumulus Bons”) attributed to a certain customer, identified by the Cumulus number.
Cumulus number.
Match pattern:^\d{13}$
>= 13 characters<= 13 characters
Example:2099123456789
Lists of UCBs attributed to the customer.
Personalized UCB information of a user based on ReTi.
Value of this UCB in CHF.
Allowed values:51020
Example:5
Valid until (including) this date.
Example:2025-09-30+02:00
The actual UCB-ID that identifies the individual UCB. This ID is the number/barcode printed on the UCB.
Example:778400003621541383
Valid from (including) this date.
Example:2023-07-18+02:00
Date and time of redemption.
Example:2015-05-27T08:27:27+02:00
1 = available, 2 = activated, 3 = redeemed.
Allowed values:123
Static data of an UCB (Blauer Bon/Coupon Bon).