# Get Overview and Security Domain URLs
source: https://developer.mastercard.com/riskrecon-api/documentation/testing/integration-routes-samples/retrve-int-rts-smpl/index.md

Allows you to retrieve a list of URLs for the Overview and Security Domains of a vendor within the **Security Profile** section of the **RiskRecon web portal**.

## Pre-requisites {#pre-requisites}

Refer to the [Retrieve Overview and Security Domain URLs](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/navigation-and-access/integrationroutes/retrieve-urls/index.md) use case.

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

    GET https://api.sandbox.riskrecon.com/v1/integration/routes/{toe_id}

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

    GET https://api.riskrecon.com/v1/integration/routes/{toe_id}

## Test Cases {#test-cases}

### Test Case: Success - Retrieve a list of URLs for the Overview and Security Domains for the given TOE ID {#test-case-success---retrieve-a-list-of-urls-for-the-overview-and-security-domains-for-the-given-toe-id}

**Request**

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

```bash
curl -X 'GET' \
  'https://api.sandbox.riskrecon.com/v1/integration/routes/09918d09-8d52-4e86-a3ec-5ef4d461e2ba' \
  -H 'accept: application/json'
  -H 'Authorization: valid_JWT_token'
```

**Response**

get:

```json
{
  "links": {
    "data_loss": "https://portal.riskrecon.com/portal/vendor/9420400/security-profile/data_loss",
    "defensibility": "https://portal.riskrecon.com/portal/vendor/9420400/security-profile/defensibility",
    "dns_security": "https://portal.riskrecon.com/portal/vendor/9420400/security-profile/dns_security",
    "email_security": "https://portal.riskrecon.com/portal/vendor/9420400/security-profile/email_security",
    "governance": "https://portal.riskrecon.com/portal/vendor/9420400/security-profile/governance",
    "network_filtering": "https://portal.riskrecon.com/portal/vendor/9420400/security-profile/network_filtering",
    "overview": "https://portal.riskrecon.com/portal/vendor/9420400/overview",
    "software_patching": "https://portal.riskrecon.com/portal/vendor/9420400/security-profile/software_patching",
    "system_hosting": "https://portal.riskrecon.com/portal/vendor/9420400/security-profile/system_hosting",
    "threat_intel": "https://portal.riskrecon.com/portal/vendor/9420400/security-profile/threat_intell",
    "web_app_security": "https://portal.riskrecon.com/portal/vendor/9420400/security-profile/web_app_security",
    "web_encryption": "https://portal.riskrecon.com/portal/vendor/9420400/security-profile/web_encryption"
  },
  "toe_id": "09918d09-8d52-4e86-a3ec-5ef4d461e2ba",
  "toe_short_name": "Fisher LLC"
}
```

### Test Case: Fail - Invalid JSON Web Token {#test-case-fail---invalid-json-web-token}

**Request**

Here is an example of a request made with an invalid JSON Web Token using a `curl` command.

```bash
curl -X 'GET' \
  'https://api.sandbox.riskrecon.com/v1/hosts/09918d09-8d52-4e86-a3ec-5ef4d461e2ba' \
  -H 'accept: application/json'
  -H 'Authorization: invalid_JWT_token'
```

**Response**

HTTP Error response 401

```json
{
  "Errors": {
    "Error": [
      {
        "Description": "Unauthorized request",
        "Details": "Invalid JWT",
        "ReasonCode": "UNAUTHORIZED",
        "Recoverable": false,
        "Source": "RISKRECON_API"
      }
    ]
  }
}
```