Dintero API (LATEST)

API Integration Support: integration@dintero.com License: UNLICENSED

API for managing Receipts, Discounts, Customers, Wallets and Webhooks


The Dintero API is organized around REST. Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which are understood by off-the-shelf HTTP clients. We support cross-origin resource sharing, allowing you to interact securely with our API from a client-side web application (though you should never expose your secret API key in any public website's client-side code). JSON is returned by all API responses, including errors.

To make the API as explorable as possible, accounts have test mode and live mode API keys. There is no "switch" for changing between modes, just use the appropriate key to perform a live or test transaction. Requests made with test mode incur no cost.


All notable changes to the API.


Extend the AccountCompany with email and technical_email

Add setting for require verification when updating user phone_number. Prevent all update of user phone_number without completing a verification via SMS.

Add support for offering_constraint_id when giving discount to one or more customers. The new optional can be used to constrain how many times the customer will receive the discount.

Fix the documentation for the response from listing customer receipts. The receipts response was missing receipt items.


Adds proxy to enhetsregisteret.


Add support for attributes_keys and attributes_values query parameters for filtering customer users

Extend discount statistics with current_stamp


Add support for enabling automatic tokens when phone numbers or emails change


Add support for applicant.agreement.attachments

Add support for enabling MFA (OOB) for auth users.

Add support for adding requirements for MCC ranges, and currencies in discounts.

Add support for adding usage ref (usage, stamp, amount) to a customer discount ref.

Add support for discount rules with discount_code. The discount_code must be included in the purchase, either in the new discount_code property or as an item, where the item id is set to the discount_code.

Add support for no_customer_id query parameter when listing public discount rules.


Extend the AccountApplicant with support for promo_code and utm campaign codes.

Add support for specifying requirement.store when creating new discount rules.

Add support for giving discounts on purchase with no customer_id.

Add support for updating rules requirement.purchase_to.

Add support for token_expire_days parameter when creating receipt. The token added to the receipt can be used to retrieve and claim it.


Add support for creating client with description

Improve documentation for receipt receipt_id property, a non-empty value is required when creating receipts.


Change minumum number of mixes in a discount rule from 2 to 1


Extend settings with PayEx connections

Extends settings with support for configuring users customer_id_format.

Extends the TokenEvent definition with `expires_at read only property.

Extends settings with support for configuring token events expiry


Add new endpoints for managing PayEx connection

Add new endpoint for deleting a tag

Exclude statistics, usage and stamp count and more in response from:

Add new endpoint for retrieving discount usages

Extend the receipt format with store.mcc property, a four-digit merchant category code for classifying the merchant