Identity Type Auto Generated Value Recipe
š Purpose
After setting up your retailer brand in AIR, a default set of identity types will be created, including CARD, CONSUMER_ID, MOBILE and EMAIL. This recipe guides you through creating an additional identity type for your organization where auto generated identity values are required. This setup will allow for the value of the identity to be auto generated and define the available variables that can be used to customize the value to your requirements. A wallet Identity is a way to identify themselves as a loyalty member across various channels.
See the Create Identity Type API reference for additional options that can be configured against identities.
š¼ Recipe Overview
In this recipe, you will set up an additional identity for a member ID that has requirements for specific characters to be generated. We will use a mix of wildcards for any numeric value and set placeholders for upper case letters. After all steps are completed, your brand will have a new identity type that can be created and used across the Eagle Eye platform and available in the wallet.
š Prerequisites
Ensure you have:
- Access to Eagle Eye APIs
- Your company unitās clientId and secret
- The unitId for your top-level company brand
- Name for the new identity type
š¤ Outputs
As you complete each step, note these outputs for future API calls and program validation:
| Output Name | Purpose |
|---|---|
| Id | Identifies each identityType you create |
š Steps
Step 1: Create Your Identity Type
- 1.1 Choose a name for your new identity type. We will use MEMBER_ID for this example.
- 1.2 Define auto generate format
| * | any alphanumeric character, numbers or letters only |
| ^ | 0-9, letters except i and o |
| # | any digit |
| ~ | any digit exclude 0 (zero) |
| A | any upper case letter |
| X | upper case A-Z expect I and o |
| C | check digit |
- 1.3 Recommended configurations:
- defaultState: EARNBURN
- defaultState: ACTIVE
Step 2: Call POST /units/unitId/walletConfig/identityTypes
unitId/walletConfig/identityTypesSend the setup request to create your identity type in the platform.
- 2.1 Use the POST /units/
unitId/walletConfig/identityTypes endpoint - 2.2 Pass in your company's unitId value in the request URL
{
"name": "MEMBER_ID",
"configuration": {
"defaultStatus": {
"value": "ACTIVE"
},
"defaultState": {
"value": "EARNONLY"
},
"format": {
"value": "A#######~"
},
"autoGenerateValueFlag": {
"value": true
},
"allowInputValueFlag": {
"value": true
},
"maxGenerationAttempts": {
"value": 3
}
}
}{
"id": "21674",
"name": "MEMBER_ID",
"configuration": {
"defaultStatus": {
"value": "ACTIVE"
},
"defaultState": {
"value": "EARNONLY"
},
"format": {
"value": "A#######~"
},
"autoGenerateValueFlag": {
"value": true
},
"allowInputValueFlag": {
"value": true
},
"maxGenerationAttempts": {
"value": 3
}
}
}Repeat this step for every identity type needed.
ā
Business Readiness Checklist
Use these checks to confirm your identity type is set up correctly:
- Create a new identity in a wallet using Create Wallet Identity
- Verify auto generate rules are working as new identities are created
- Verify default state and status are set upon create of a new identity in a wallet if the state and status are left out of the create identity request
š§ Troubleshooting Tips
| Issue | Possible Cause & Resolution |
|---|---|
| Unit Not Found (UNF) | The unit may not be the parent for the clientId used. Verify your unitId, clientId and secret before retrying. |
| IR: Invalid request date Error | The identity name in the request already exists. Use a unique name for the new identity type. |
Updated about 5 hours ago
