# Update Risk Relationship Folder Names and Slugs
source: https://developer.mastercard.com/riskrecon-api/documentation/testing/toe-samples/updt-risk-reln-fold-smpl/index.md

Allows you to move a TOE to another risk relationship folder within your portfolio.

## Pre-requisites {#pre-requisites}

Refer to the [Update the Risk Relationship Folder of a TOE](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/portfolio-management/portfolio/update-risk-reln-fold-toe/index.md) use case.

## Request URL for the Sandbox environment {#request-url-for-the-sandbox-environment}

    PUT https://api.sandbox.riskrecon.com/v1/toes/risk_relationships

## Request URL for the Production environment {#request-url-for-the-production-environment}

    PUT https://api.riskrecon.com/v1/toes/risk_relationships

## Test Cases {#test-cases}

### Test Case: Success - Move TOEs to another risk relationship folder {#test-case-success---move-toes-to-another-risk-relationship-folder}

**Request**

Here is an example of a request made using a `curl` command.

```bash
curl -X 'PUT' \
  'https://api.riskrecon.com/v1/toes/risk_relationships' \
  -H 'accept: application/json' \
  -H 'Authorization: valid_JWT ' \
  -H 'Content-Type: application/json' \
  -d '{
  "risk_relationship_slugs": [
    "communityportfolio_high"
  ],
  "toe_id": "09918d09-8d52-4e86-a3ec-5ef4d461e2ba"
}'
```

**Response**

put:

```json
{
  "risk_relationship_slugs": [
    "communityportfolio_high"
  ],
  "toe_id": "09918d09-8d52-4e86-a3ec-5ef4d461e2ba"
}
```

### Test Case: Fail - Missing TOE ID {#test-case-fail---missing-toe-id}

**Request**

Here is an example, using a `curl` command, of a request made without providing the `toe_id`.

```bash
curl -X 'PUT' \
  'https://api.riskrecon.com/v1/toes/risk_relationships' \
  -H 'accept: application/json' \
  -H 'Authorization: valid_JWT ' \
  -H 'Content-Type: application/json' \
  -d '{
  "risk_relationship_slugs": [
    "ownenterprise_critical"
  ]
}'
```

**Response**

HTTP Error Response 400

```json
{
  "Errors": {
    "Error": [
      {
        "Description": "Bad Request",
        "Details": "toe_id: can't be blank",
        "ReasonCode": "BAD_REQUEST",
        "Recoverable": false,
        "Source": "RISKRECON_API"
      }
    ]
  }
}
```

### Test Case: Fail - Missing Risk Relationship Slug {#test-case-fail---missing-risk-relationship-slug}

**Request**

```bash
curl -X 'PUT' \
  'https://api.riskrecon.com/v1/toes/risk_relationships' \
  -H 'accept: application/json' \
  -H 'Authorization: valid_JWT ' \
  -H 'Content-Type: application/json' \
  -d '{
  "toe_id": "09918d09-8d52-4e86-a3ec-5ef4d461e2ba"
  }'
```

**Response**

HTTP Error Response 400

```json
{
  "Errors": {
    "Error": [
      {
        "Description": "Bad Request",
        "Details": "risk_relationship_slugs: can't be blank",
        "ReasonCode": "BAD_REQUEST",
        "Recoverable": false,
        "Source": "RISKRECON_API"
      }
    ]
  }
}
```

### Test Case: Fail - User missing RiskClassifier scope {#test-case-fail---user-missing-riskclassifier-scope}

**Request**

A user who does not have the **RiskClassifier** scope tries to move TOEs to another risk relationship folder in the portfolio.

**Response**

HTTP Error response 401

```json
{
  "Errors": {
    "Error": [
      {
        "Description": "Unauthorized request",
        "Details": "User must have RiskClassifier scope",
        "ReasonCode": "UNAUTHORIZED",
        "Recoverable": false,
        "Source": "RISKRECON_API"
      }
    ]
  }
}
```