# Use Cases
source: https://developer.mastercard.com/token-requestor-identifier-api/documentation/use-cases/index.md

In MDES [On-Behalf-Of (OBO) model](https://developer.mastercard.com/mdes-digital-enablement/documentation/use-cases/mdes-for-merchants-on-behalf-of-model-use-cases/), an On-behalf-Of Token Requestor (OBOTR) must provide a unique Token Requestor ID (TRID) for each Token Requestor when making the MDES API requests for Tokenization. TRIDs can be obtained and managed via the TRID API. The three main use-cases TRID API supports are:

[Create TRID](https://developer.mastercard.com/token-requestor-identifier-api/documentation/use-cases/create-a-token-requestor/index.md)

[Update Token Requestor Attributes](https://developer.mastercard.com/token-requestor-identifier-api/documentation/use-cases/update-a-token-requestor/index.md)

[Search for a Token Requestor](https://developer.mastercard.com/token-requestor-identifier-api/documentation/use-cases/search-for-a-token-requestor/index.md)