Zum Inhalt springen
meniodevelopermenio DashboardVorschau

Profile Activation API

API-REFERENZ

Profile Activation API

Historische Vorbereitung der Kartenaktivierung im Einzelhandel.

Archiv2 Endpunkte
Blueprint
Laut Confluence ohne Verwendung; historischer Projektstand.
BASE URLhttps://pos.api.qnips.com/api/pos/v3
Grundlagen & vollständige Einführung

General Information

The menio Profile Activation API can be used to activate prebuilt profiles when needed.
There are two different environments for this API:

To use this API, you will need a hexadecimal DevKey, provided by qnips. With it, the API will identify your client as a requestor. Your key is valid for both environments, LIVE and STAGING. Please ask your primary contact at menio for your personal DevKey.

Generating a SecurityToken

As the process of activation of a pregenerated profile is a sensible operation, the process involves a special SecurityToken which needs to be generated individually for each Call of this API. It must be generated by a special algorithm described below.

  • build a String with profileId + „ac39d745a3a540a294ec46200ed3d696“ + DevKey with no whitespaces in between:

    • profileId: the Id of the profile which is to be activated. Usually, this will be the token on a given medium (e.g. a barcode printed on a gift card or a customer's QR code in an app).
    • „ac39d745a3a540a294ec46200ed3d696“: a constant string
    • DevKey: your developer key assigned to your organisation by menio

    Example:

    with input=„123456“ and DevKey=„af87b1“ the result string should be: „123456ac39d745a3a540a294ec46200ed3d696af87b1“

  • now build the MD5-Hash for the result of the previous step.

    For the example value of step 1 the Hash would be „3f70267c85aae2d893321a68a52ae9f8“

  • This Hash value is your individual SecurityToken which must be set as the Header of each activation call.