Voucher

Vouchers are mainly described by the voucher group they belong to. Shared vouchers can be redeemed multiple times and as such never changes its status to redeemed. Unique vouchers have unique codes for each user and can only be redeemed once.

voucherId ✓

integer (as string)

Unique ID of the voucher. Endpoints only ever use the voucherCode to access vouchers

voucherGroupId ✓

integer (as string)

ID of the voucher group the voucher belongs to

userId ✓

integer (as string)

userId of the user that redeemed the voucher or that the voucher is handed out to

type ✓

Voucher type

Voucher group type

count

integer (as string)

Number of time the voucher has been redeemed. Only available for shared vouchers.

voucherCode ✓

string

A unique string that gives access to this voucher

status ✓

Voucher status

handoutBy ✓

integer (as string)

userId of the user that handed out the voucher

createdBy ✓

integer (as string)

userId of the user that generated the voucher

updated ✓

datetime

When the voucher was last updated (i.e. had its status changed)

created ✓

datetime

When the voucher was created

The check mark ✓ indicates that the field always contains a valid non-empty value.

Comments/feedback

Do you have questions, or just want to contribute some newly gained insight? Want to share an example? Please leave a comment. Our team reads and responds to every question. Additionally, your experience can help others using Schibsted account, and it can help us continuously improve our documentation.

Relevant endpoints