---
title: "Create an Edge Config token"
method: POST
path: "/v1/edge-config/{edgeConfigId}/token"
tags: ["edge-config"]
---

# Create an Edge Config token

`POST /v1/edge-config/{edgeConfigId}/token`

Adds a token to an existing Edge Config.

## Path parameters

- `edgeConfigId` string, required

## Query parameters

- `teamId` string
- `slug` string

## Request body

- object
  - `label` string, required

## Response `201`

- object
  - `token` string, required
  - `id` string, required

## Other responses

- `400` — One of the provided values in the request body is invalid. One of the provided values in the request query is invalid.
- `401` — The request is not authorized.
- `402` — The account is missing a payment so payment method must be updated
- `403` — You do not have permission to access this resource.
- `404`
- `409`
- `410`

## Changes

- **2026-07-21** `2ae10ee9d21c` — 1 info
  - added the non-success response with the status `410`

[Change history](https://skmtc.dev/vercel/apis/api/changes/v1/edge-config/:edgeConfigId/token/post.md)

---

[API](https://skmtc.dev/vercel/apis/api.md) · [All operations](https://skmtc.dev/vercel/apis/api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/vercel/api/revisions/dc85585fad8d/schema)