User Optins

Calls mentioned would require client_access_token in the Request header alongside the nonce from the previous step

A call to endpoint

GET /api/1/user/optins?locale={{locale}}

would determine the optins that are needed to complete the registration process.

response

{
    "auth_nonce": "<NONCE>",
    "identifier": "<CARD_NUMBER>"
}

Using the required optin_ids from the previous call, and using the nonce from the previous step, another call to endpoint

PUT /api/1/user/optins/change?locale={{locale}} 

with the sample payload would allow saving the optins for the user

{
    "auth_nonce": "<NONCE>",
    "optins": [
        {
            "optin_id": "<OPTIN_ID>",
            "optin": true
        },
        {
            "optin_id": "<OPTIN_ID>",
            "optin": true
        }
    ]
}

Note that optin must be true to the required optin_ids in order to complete this step.