# Create TRID
source: https://developer.mastercard.com/token-requestor-identifier-api/documentation/use-cases/create-a-token-requestor/index.md

The TRID API allows you to obtain TRIDs for multiple Token Requestors in a single request. This use case explains how to get a TRID for each merchant that a PSP is operating on behalf of. The TRID API accepts Token Requestor information from the OBOTR in the inbound Batch Create Token Requestors API request.

The high-level flow for TRID provisioning and assignment is as below:
Diagram trid-create

### Endpoint {#endpoint}


API Reference: `POST /token-requestors/batches`

Note: If you are a Digital Activity Service Provider (DASP) intending to request TRIDs for other OBOTRs, customerId of an OBTOR can be passed in as an additional field in the **tokenRequestors** array object for every merchant. TRID(s) generated via this type of request will be mapped to the specific customerId present in each payload object. Additional client onboarding steps are needed to enable this functionality. Reach out to your CIS representative for help. For a definition of a Digital Activity Service Provider (DASP), see [FAQs](https://developer.mastercard.com/token-requestor-identifier-api/documentation/support/index.md#on-board-a-token-requestor-create-trid)