# Update the Internal Identities of a TOE
source: https://developer.mastercard.com/riskrecon-api/documentation/use-cases/portfolio-management/portfolio/update-a-toe-internal-id/index.md

## Overview {#overview}

The `PUT TOE` endpoint allows you to map a TOE ID to an identifier used for the vendor within your internal systems. Using this endpoint, you can update the [internal ID](https://developer.mastercard.com/riskrecon-api/documentation/glossary/index.md#internal-ids), the [internal names](https://developer.mastercard.com/riskrecon-api/documentation/glossary/index.md#internal-name), or both of a TOE in your portfolio. You can add multiple internal identities of a TOE using this endpoint.

You need to input the `toe_id` as the request parameter and the desired internal identities into the request body to be able to update a TOE in your portfolio.

## Sequence Diagram {#sequence-diagram}

The following diagram shows how to update an existing TOE in your portfolio:
Diagram update-a-toe

## Execution Steps {#execution-steps}

The following steps describe how to update an existing TOE in your portfolio:

1. The user sends a `PUT` request to update the internal identities of a TOE in their portfolio and provides the `toe_ id` as the input parameter.
2. RiskRecon updates the internal identities of the requested TOE in the user's portfolio.

## Sample Request and Response {#sample-request-and-response}

For a sample response for this API, see [Put the Internal Identities of a TOE](https://developer.mastercard.com/riskrecon-api/documentation/testing/toe-samples/updt-a-toe-intl-id-smpl/index.md).

## Use Case Example {#use-case-example}

The use case [Update multiple internal identities of TOEs](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/portfolio-management/portfolio/update-a-toe-internal-id/index.md#update-toes-with-multiple-internal-identities) discusses how you can use the `PUT TOE` endpoint to update TOEs with multiple internal identities:

### Update multiple internal identities of TOEs {#update-multiple-internal-identities-of-toes}

An organization has two departments, namely, the Vendor Management department and the Risk Management department. Each department maintains their own database of vendors and provides their own unique identifier to each vendor. The Vendor Management department has already updated the TOEs with the unique identifiers they use to identify each TOE. The Risk Management department also wants to update each TOE with different identifiers that they use for each TOE and can use the `PUT TOE` endpoint to do the same.

It is important to note that the Risk Management department could end up replacing the internal TOE IDs of the Vendor Management department altogether if they are not careful. If the user wants a vendor to have multiple IDs, then it is a good practice to input all the IDs in the request body so that updates are done correctly.

## Endpoint {#endpoint}


API Reference: `PUT /v1/toe/{toe_id}`