# Add an Existing TOE to your Portfolio
source: https://developer.mastercard.com/riskrecon-api/documentation/use-cases/portfolio-management/portfolio/add-an-existing-toe/index.md

## Overview {#overview}

The `POST TOE` endpoint instantly adds an [existing TOE](https://developer.mastercard.com/riskrecon-api/documentation/glossary/index.md#toe) to your portfolio using TOE IDs. You can add only one TOE at a time using this endpoint.

You must provide the `toe_id` as the request parameter to add the TOE to your portfolio. Using this endpoint, you can also add TOE details through the request body. The TOE details could include information, such as, risk relationship slug, assessment frequency, internal names and ID, and subscription level.

The `Portfolio Bulk Add` endpoint can also be used to add existing TOEs to your portfolio, however, the recommended use for the bulk add endpoint is to add new TOEs that RiskRecon does not currently monitor and need to be created by a security analyst.
For more details on the `POST Bulk Add` endpoint, refer to the [Add TOEs in bulk to your Portfolio](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/portfolio-management/portfolio/add-bulk-toes/index.md) use case.
Note: If you are not aware of the TOE ID, you can use the `GET TOEs By Domain` endpoint to obtain the TOE ID before executing the `POST TOE` endpoint. For more details on the `GET TOEs By Domain` endpoint, refer to the [Retrieve a TOE by a Domain or Hostname](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/portfolio-management/portfolio/retrieve-toe-by-domain/index.md) use case.

## Sequence Diagram {#sequence-diagram}

The following diagram shows how to add an existing TOE to your portfolio:
Diagram add-existing-toe

## Execution Steps {#execution-steps}

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

1. The user sends a `POST` request to add an existing TOE to the portfolio and provides the `toe_id` as the input parameter.
2. RiskRecon adds the requested TOE to the user's portfolio.

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

For a sample response of this API, see [Post an Existing TOE to your Portfolio](https://developer.mastercard.com/riskrecon-api/documentation/testing/toe-samples/add-an-exist-toe-smpl/index.md).

## Use Case Examples {#use-case-examples}

The [Add a TOE when the TOE ID is not known](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/portfolio-management/portfolio/add-an-existing-toe/index.md#add-a-toe-when-the-toe-id-is-not-known) use case discusses how you can use the `POST TOE` endpoint to add TOEs to your portfolio.

### Add a TOE when the TOE ID is not known {#add-a-toe-when-the-toe-id-is-not-known}

A RiskRecon customer needs to add a TOE to their portfolio, but they only have the TOE domain and not the TOE ID. The customer can use the `GET TOE by Domain` endpoint to search for a TOE by a valid domain. Once the customer has the TOE ID, then the customer can use the `POST TOE` endpoint to add the TOE to the portfolio. If there are no results returned when the customer searches by domain, the customer may decide to submit a bulk add request to have a RiskRecon security analyst build the TOE and add it to their portfolio.

## Endpoint {#endpoint}


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