2 - Whitelist investor(s) for a token

POST {{base_url_servicing}}/tokens/{{token_id}}/holders/whitelist

https://docs.tokeny.com/docs/qualify-new-investors

https://docs.tokeny.com/reference/post_tokens-tokenid-holders-whitelist

STEP 2:

This endpoint does not need an agent signature, with the agent wallet such as MetaMask... Because Tokeny is the one managing the qualification on the agent behalf.

Whitelisting is an onchain operation that:

1. Create and deploy an ONCHAINID (OID) (if the email address is not yet linked to one).

2. Add the wallet as key of that ONCHAINID (if it has not been added before).

3. Issue the claim(s) required by the ERC-3643, on the OID.

4. Whitelist that [ONCHAINID ↔ wallet address] pair on the ERC-3643 Identity Registry smart contract (if it has been previously added, endpoint will throw a validation error).

After this endpoint, the investor should appear in the front, but it can take some time; you can do a Get a Holder to see the status of an investor.

Parameters

  • oken_id: The identifier of the T-REX
  • jwt: The authentication token
  • identityIds: The array of identities to whitelist, as retrieved after import.
  • wallets: The addresses of the wallets linked to the identities.
    If you wish to generate an ONCHAINID wallet for one of the identities, leave this entry to null (index of the wallet should match the index of the identityId)

Response:

One whitelistingId per batch

Request Body

{"identityIds"=>["eeedb5a6-8e2f-45c4-b0c3-d1070fe9699e"], "wallets"=>["0x0de68aae8b95cf79352dcb01477b52d95e395297"]}