---
title: "Create a token for a service account."
method: POST
path: "/api/admin/service-account/{id}/token"
tags: ["Service Accounts"]
---

# Create a token for a service account.

`POST /api/admin/service-account/{id}/token`

**Enterprise feature**

Creates a new token for the service account identified by the id.

## Path parameters

- `id` string, required

## Request body

- CreatePatSchema — Describes the properties required to create a [personal access token](https://docs.getunleash.io/concepts/api-tokens-and-client-keys#personal-access-tokens), or PAT. PATs are automatically scoped to the authenticated user.
  - `description` string, required — The PAT's description.
  - `expiresAt` string, date-time, required — The PAT's expiration date.

## Response `201`

The resource was successfully created.

- PatSchema — Describes a [personal access token](https://docs.getunleash.io/concepts/api-tokens-and-client-keys#personal-access-tokens), or PAT. PATs are automatically scoped to the authenticated user.
  - `id` integer, required — The PAT's ID. PAT IDs are incrementing integers. In other words, a more recently created PAT will always have a higher ID than an older one.
  - `secret` string — The token used for authentication. It is automatically generated by Unleash when the PAT is created and that is the only time this property is returned.
  - `createdAt` string, date-time, required — The date and time of when the PAT was created.
  - `seenAt` string, date-time, nullable — When the PAT was last seen/used to authenticate with. `null` if it has not been used yet.
  - `userId` integer — The ID of the user this PAT belongs to.
  - `description` string, required — The PAT's description.
  - `expiresAt` string, date-time, required — The PAT's expiration date.

## Other responses

- `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
- `404` — The requested resource was not found.
- `409` — The provided resource can not be created or updated because it would conflict with the current state of the resource or with an already existing resource, respectively.
- `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)