Enum - Usecases

Full Url

Arguments

  • token (required)

Info

This list contains all TCR defined use-cases. Use-cases are grouped into two classes: STANDARD and SPECIAL. STANDARD use-cases are generally available to brand without brand vetting. SPECIAL use-cases, on the other hand, may require brand vetting and/or MNO review.
A brand may not qualify for all STANDARD use-cases. CSP may consider brand vetting to achieve access to broader use-cases.
Some use-cases require additional declaration of sub-usecases. If the chosen use-case's 'minsubusecase' attribute is greater than 0, then the additional sub-use-case declaration is mandatory during campaign submission. The number of sub-use-cases required must be between 'minsubusecase' and 'maxsubusecase'.

Example Success

{
code: 200,
status: "success",
data: {
"2FA":{
"classification":"STANDARD",
"description":"Two-Factor authentication, one-time use password, password reset",
"display_name":"2FA",
"max_sub_usecases":0,
"min_sub_usecases":0,
"valid_sub_usecase":true,
"cost":10
},
"ACCOUNT_NOTIFICATION":{
"classification":"STANDARD",
"description":"All reminders, alerts, and notifications. (Examples include: flight delayed, hotel booked, appointment reminders.)",
"display_name":"Account Notification",
"max_sub_usecases":0,
"min_sub_usecases":0,
"valid_sub_usecase":true,
"cost":10
},
"AGENTS_FRANCHISES":{
"classification":"SPECIAL",
"description":"For brands that have multiple agents, franchises or offices in the same brand vertical, but require individual localised numbers per agent\/location\/office. Final fees are under review",
"display_name":"Agents and Franchises",
"max_sub_usecases":0,
"min_sub_usecases":0,
"valid_sub_usecase":false,
"cost":30
},
....
}
}