---
title: "[BETA] Create a signal endpoint token for a specific signal endpoint."
method: POST
path: "/api/admin/signal-endpoints/{signalEndpointId}/tokens"
tags: ["Operational"]
---

# [BETA] Create a signal endpoint token for a specific signal endpoint.

`POST /api/admin/signal-endpoints/{signalEndpointId}/tokens`

**Enterprise feature**

**[BETA]** This API is in beta state, which means it may change or be removed in the future.

Creates a new signal endpoint token for a specific signal endpoint, identified by its id.

## Path parameters

- `signalEndpointId` string, required

## Request body

- CreateSignalEndpointTokenSchema — Describes the properties required to create or update a signal endpoint token.
  - `name` string, required — The signal endpoint token name.

## Response `201`

The resource was successfully created.

- SignalEndpointTokenSchema — An object describing a signal endpoint token.
  - `id` integer, required — The signal endpoint token's ID. Signal endpoint token IDs are incrementing integers. In other words, a more recently created signal endpoint token will always have a higher ID than an older one.
  - `token` string — The token used for authentication. It is automatically generated by Unleash when the token is created and that is the only time this property is returned.
  - `name` string, required — The signal endpoint token name.
  - `signalEndpointId` integer, required — The signal endpoint ID that this token belongs to.
  - `createdAt` string, date-time, required — The date and time of when the signal endpoint token was created.
  - `createdByUserId` integer, required — The ID of the user that created this signal endpoint token.

## Other responses

- `400` — The request data does not match what we expect.
- `401` — Authorization information is missing or invalid. Provide a valid API token as the `authorization` header, e.g. `authorization:*.*.my-admin-token`.
- `403` — The provided user credentials are valid, but the user does not have the necessary permissions to perform this operation
- `415` — The operation does not support request payloads of the provided type. Please ensure that you're using one of the listed payload types and that you have specified the right content type in the "content-type" header.

---

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