# Create a service account token **POST /_security/service/{namespace}/{service}/credential/token/{name}** **All methods and paths for this operation:**
POST /_security/service/{namespace}/{service}/credential/token
PUT /_security/service/{namespace}/{service}/credential/token/{name}
POST /_security/service/{namespace}/{service}/credential/token/{name}
Create a service accounts token for access without requiring basic authentication. NOTE: Service account tokens never expire. You must actively delete them if they are no longer needed. ## Required authorization * Cluster privileges: `manage_service_account` [External documentation](https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/service-accounts) ## Servers - http://api.example.com: http://api.example.com () ## Authentication methods - Api key auth - Basic auth - Bearer auth ## Parameters ### Path parameters - **namespace** (string) The name of the namespace, which is a top-level grouping of service accounts. - **service** (string) The name of the service. - **name** (string) The name for the service account token. If omitted, a random name will be generated. Token names must be at least one and no more than 256 characters. They can contain alphanumeric characters (a-z, A-Z, 0-9), dashes (`-`), and underscores (`_`), but cannot begin with an underscore. NOTE: Token names must be unique in the context of the associated service account. They must also be globally unique with their fully qualified names, which are comprised of the service account principal and token name, such as `//`. ### Query parameters - **refresh** (string) If `true` then refresh the affected shards to make this operation visible to search, if `wait_for` (the default) then wait for a refresh to make this operation visible to search, if `false` then do nothing with refreshes. ## Responses ### 200 #### Body: application/json (object) - **created** (boolean) - **token** (object) [Powered by Bump.sh](https://bump.sh)