# Get Display Names for Security Domains
source: https://developer.mastercard.com/riskrecon-api/documentation/testing/displaynames-samples/sec-dom-disp-nms-smpl/index.md

Allows you to retrieve a one-to-one mapping of each security domain name as they are presented in the API response and the RiskRecon web portal.

## Pre-requisites {#pre-requisites}

Refer to the [Retrieve Display Names for Security Domains](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/navigation-and-access/displayname/rtreve-disp-nm-sec-dom/index.md) use case.

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

    https://api.sandbox.riskrecon.com/v1/display_names/security_domain

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

    https://api.riskrecon.com/v1/display_names/security_domain

## Test Cases {#test-cases}

### Test Case: Success - Retrieve display names for security domains {#test-case-success---retrieve-display-names-for-security-domains}

**Request**

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

```bash
curl -X 'GET' \
  'https://api.sandbox.riskrecon.com/v1/display_names/security_domain' \
  -H 'accept: application/json' \
  -H 'Authorization: valid_JWT_token' \'
```

**Response**

get:

```json
[
  {
    "deprecated": false,
    "display_name": "Breach Events",
    "name": "data_loss",
    "rated": true
  },
  {
    "deprecated": false,
    "display_name": "System Hosting",
    "name": "defensibility",
    "rated": true
  },
  {
    "deprecated": false,
    "display_name": "DNS Security",
    "name": "dns_security",
    "rated": true
  },
  {
    "deprecated": false,
    "display_name": "Email Security",
    "name": "email_security",
    "rated": true
  },
  {
    "deprecated": true,
    "display_name": "Governance",
    "name": "governance",
    "rated": false
  },
  {
    "deprecated": false,
    "display_name": "Network Filtering",
    "name": "network_filtering",
    "rated": true
  },
  {
    "deprecated": false,
    "display_name": "Software Patching",
    "name": "software_patching",
    "rated": true
  },
  {
    "deprecated": true,
    "display_name": "System Hosting",
    "name": "system_hosting",
    "rated": true
  },
  {
    "deprecated": false,
    "display_name": "System Reputation",
    "name": "threat_intell",
    "rated": true
  },
  {
    "deprecated": false,
    "display_name": "Application Security",
    "name": "web_app_security",
    "rated": true
  },
  {
    "deprecated": false,
    "display_name": "Web Encryption",
    "name": "web_encryption",
    "rated": true
  }
]
```

### Test Case: Fail - Incorrect endpoint name {#test-case-fail---incorrect-endpoint-name}

**Request**

Here is an example, using a `curl` command, of a request made with the endpoint name spelt incorrectly.

```bash
curl -X 'GET' \
  'https://api.sandbox.riskrecon.com/v1/display_names/securitydomain' \
  -H 'accept: application/json' \
  -H 'Authorization: valid_JWT_token' \'
```

**Response**

HTTP Error Response 404

```json
{
    "Errors": {
        "Error": [
            {
                "Description": "Resource Not found.",
                "Details": null,
                "ReasonCode": "NOT_FOUND",
                "Recoverable": false,
                "Source": "RISKRECON_API"
            }
        ]
    }
}
```