---
title: TLS Configuration
summary: Customers with access to multiple sets of IP pools can apply different configuration options to their TLS-enabled domains.
url: https://www.fastly.com/documentation/reference/api/ip-configuration/spp/tls-configuration
---

Customers with access to multiple sets of IP pools can apply different configuration options to their TLS-enabled domains.

## Data model

| Field | Type | Description |
|-------|------|-------------|
| `http_protocols` | array | HTTP protocols available on your configuration. At least one protocol is required:  <code>http/1.1</code> is always supported and is required in the array. <code>http/2</code> is optionally supported in the array. <code>http/3</code> is optionally supported in the array. |
| `name` | string | A custom name for your TLS configuration. Optional, we will assign a value to this if none is provided. |
| `tls_1_2_cipher_suite_profile` | array | An ordered collection of OpenSSL-formatted cipher suite names used for TLS-1.0, TLS-1.1 and TLS-1.2 protocol versions.  <strong>Note:</strong> Setting this field is an advanced feature that requires enablement by <a href="https://support.fastly.com/hc/en-us#open-chat">Fastly Support</a>. |
| `tls_protocols` | array | TLS protocols available on your configuration. The following TLS protocols are supported:  [“1.0”, “1.1”, “1.2”]  [“1.0”, “1.1”, “1.2”, “1.3”]  [“1.0”, “1.1”, “1.2”, “1.3+0RTT”]  [“1.2”] [“1.2”, “1.3”] [“1.2”, “1.3+0RTT”]. |
| `vipspace` | string | A Fastly assigned name representing a set of network prefixes that are available for operations like acquiring TLS configurations. This field is Required, and must be <code>customer_assigned_vipspace</code>. |

## Data model

| Field | Type | Description |
|-------|------|-------------|
| `http_protocols` | array | HTTP protocols available on your configuration. At least one protocol is required:  <code>http/1.1</code> is always supported and is required in the array. <code>http/2</code> is optionally supported in the array. <code>http/3</code> is optionally supported in the array. |
| `name` | string | A custom name for your TLS configuration. Optional, we will assign a value to this if none is provided. |
| `relationships.default_certificate.id` | string | Alphanumeric string identifying the default TLS certificate. |
| `relationships.default_ecdsa_certificate.id` | string | Alphanumeric string identifying the default ECDSA TLS certificate. |
| `relationships.dns_records.id` | string | The IPv4 address that will be used for your TLS configuration. <strong>Note:</strong> Setting this field is an advanced feature that requires enablement by <a href="https://support.fastly.com/hc/en-us#open-chat">Fastly Support</a>. |
| `relationships.service.id` | string | Alphanumeric string identifying the service. |
| `tls_1_2_cipher_suite_profile` | array | An ordered collection of OpenSSL-formatted cipher suite names used for TLS-1.0, TLS-1.1 and TLS-1.2 protocol versions.  <strong>Note:</strong> Setting this field is an advanced feature that requires enablement by <a href="https://support.fastly.com/hc/en-us#open-chat">Fastly Support</a>. |
| `tls_protocols` | array | TLS protocols available on your configuration. The following TLS protocols are supported:  [“1.0”, “1.1”, “1.2”]  [“1.0”, “1.1”, “1.2”, “1.3”]  [“1.0”, “1.1”, “1.2”, “1.3+0RTT”]  [“1.2”] [“1.2”, “1.3”] [“1.2”, “1.3+0RTT”]. |
| `type` | string | Resource type. |
| `vipspace` | string | A Fastly assigned name representing a set of network prefixes that are available for operations like acquiring TLS configurations. This field is Required, and must be <code>customer_assigned_vipspace</code>. |

## Data model

| Field | Type | Description |
|-------|------|-------------|
| `bulk` | boolean | Signifies whether the configuration is used for Platform TLS or not. We will always assume for this product  that the value for this is “false”, signifying you have full access to the main set of APIs for custom  <a href="https://developer.fastly.com/reference/api/tls/custom-certs/">TLS certificates</a> and  <a href="https://developer.fastly.com/reference/api/tls/subs/">TLS subscriptions</a>, as well as the  <a href="https://manage.fastly.com/network/domains">TLS management UI</a>. (Read-only) |
| `created_at` | string | Date and time in ISO 8601 format. (Read-only) |
| `default` | boolean | Signifies whether or not Fastly will use this configuration as a default when creating a new  <a href="https://www.fastly.com/documentation/reference/api/tls/custom-certs/activations/">TLS activation</a>. (Read-only) |
| `http_protocols` | array | HTTP protocols available on your configuration. At least one protocol is required:  <code>http/1.1</code> is always supported and is required in the array. <code>http/2</code> is optionally supported in the array. <code>http/3</code> is optionally supported in the array. |
| `id` | string | Alphanumeric string identifying a TLS configuration. |
| `name` | string | A custom name for your TLS configuration. Optional, we will assign a value to this if none is provided. |
| `relationships.default_certificate.id` | string | Alphanumeric string identifying the default TLS certificate. |
| `relationships.default_ecdsa_certificate.id` | string | Alphanumeric string identifying the default ECDSA TLS certificate. |
| `relationships.dns_records.id` | string | The IP address or hostname of the DNS record. |
| `relationships.service.id` | string | Alphanumeric string identifying the service. |
| `tls_1_2_cipher_suite_profile` | array | An ordered collection of OpenSSL-formatted cipher suite names used for TLS-1.0, TLS-1.1 and TLS-1.2 protocol versions.  <strong>Note:</strong> Setting this field is an advanced feature that requires enablement by <a href="https://support.fastly.com/hc/en-us#open-chat">Fastly Support</a>. |
| `tls_1_3_cipher_suite_profile` | array | An ordered collection of OpenSSL-formatted cipher suite names used for TLS-1.3.  If TLS-1.3 is selected, you will get the default list. (Read-only) |
| `tls_protocols` | array | TLS protocols available on your configuration. The following TLS protocols are supported:  [“1.0”, “1.1”, “1.2”]  [“1.0”, “1.1”, “1.2”, “1.3”]  [“1.0”, “1.1”, “1.2”, “1.3+0RTT”]  [“1.2”] [“1.2”, “1.3”] [“1.2”, “1.3+0RTT”]. |
| `type` | string | Resource type. |
| `updated_at` | string | Date and time in ISO 8601 format. (Read-only) |
| `vipspace` | string | A Fastly assigned name representing a set of network prefixes that are available for operations like acquiring TLS configurations. This field is Required, and must be <code>customer_assigned_vipspace</code>. |

## Data model

| Field | Type | Description |
|-------|------|-------------|
| `http_protocols` | array | HTTP protocols available on your configuration. At least one protocol is required:  <code>http/1.1</code> is always supported and is required in the array. <code>http/2</code> is optionally supported in the array. <code>http/3</code> is optionally supported in the array. |
| `name` | string | A custom name for your TLS configuration. Optional, we will assign a value to this if none is provided. |
| `relationships.default_certificate.id` | string | Alphanumeric string identifying the default TLS certificate. |
| `relationships.default_ecdsa_certificate.id` | string | Alphanumeric string identifying the default ECDSA TLS certificate. |
| `relationships.service.id` | string | Alphanumeric string identifying the service. |
| `tls_1_2_cipher_suite_profile` | array | An ordered collection of OpenSSL-formatted cipher suite names used for TLS-1.0, TLS-1.1 and TLS-1.2 protocol versions.  <strong>Note:</strong> Setting this field is an advanced feature that requires enablement by <a href="https://support.fastly.com/hc/en-us#open-chat">Fastly Support</a>. |
| `tls_protocols` | array | TLS protocols available on your configuration. The following TLS protocols are supported:  [“1.0”, “1.1”, “1.2”]  [“1.0”, “1.1”, “1.2”, “1.3”]  [“1.0”, “1.1”, “1.2”, “1.3+0RTT”]  [“1.2”] [“1.2”, “1.3”] [“1.2”, “1.3+0RTT”]. |
| `type` | string | Resource type. |

## API endpoints

### List TLS configurations

**GET** `/tls/configurations`

List all TLS configurations.

**Parameters:**

| Name | Type | In | Required | Description |
|------|------|----|---------|--------------|
| `filter[bulk]` | string | query | No | Optionally filters by the bulk attribute. |
| `include` | string | query | No | Include related objects. Optional, comma-separated values. Permitted values: <code>dns_records</code>. |
| `page[number]` | integer | query | No | Current page. |
| `page[size]` | integer | query | No | Number of records per page. |

### Create a TLS configuration

**POST** `/tls/configurations`

Create a TLS configuration.

### Get a TLS configuration

**GET** `/tls/configurations/{tls_configuration_id}`

Show a specific TLS configuration.

**Parameters:**

| Name | Type | In | Required | Description |
|------|------|----|---------|--------------|
| `include` | string | query | No | Include related objects. Optional, comma-separated values. Permitted values: <code>dns_records</code>. |
| `tls_configuration_id` | string | path | Yes | TLS Configuration ID (UUID). |

### Delete a TLS configuration

**DELETE** `/tls/configurations/{tls_configuration_id}`

Remove a TLS configuration.

**Parameters:**

| Name | Type | In | Required | Description |
|------|------|----|---------|--------------|
| `tls_configuration_id` | string | path | Yes | TLS Configuration ID (UUID). |

### Update a TLS configuration

**PATCH** `/tls/configurations/{tls_configuration_id}`

Update a TLS configuration.

**Parameters:**

| Name | Type | In | Required | Description |
|------|------|----|---------|--------------|
| `tls_configuration_id` | string | path | Yes | TLS Configuration ID (UUID). |