---
title: "Create TLS config"
method: POST
path: "/public/v2/routers/configs/tls"
tags: ["Routers"]
---

# Create TLS config

`POST /public/v2/routers/configs/tls`

Required permission: Device command and configuration, Edit.<br/>Creates a TLS config that allows this certificate and key to be used in router configs when a certificate and key are required by only specifying the certificate (matching key will be added). TLS configs are identified by their certificate string base64 encoded which must be unique on the account.

## Request body

- TlsConfigCreateRequestV2
  - `certificateBase64Pem` string, required — TLS certificate in PEM format, base64 encoded.
  - `keyBase64Pem` string, required — TLS key in PEM format, base64 encoded. Must match the public key of the certificate.

## Response `200`

Success

## Other responses

- `201` — Created
- `400` — Bad Request
- `401` — Unauthorized
- `403` — Missing required permission for this endpoint or resource
- `422` — Failed to create TLS config. Certificates must be unique.

---

[API](https://skmtc.net/starlink/apis/starlink-management-api.md) · [All operations](https://skmtc.net/starlink/apis/starlink-management-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/starlink/starlink-management-api/revisions/a730bd0ddb42/schema)