Mirrors/unleash.unleash
1
0
Fork 0
mirror of https://github.com/Unleash/unleash.git synced 2025-10-27 11:02:16 +01:00
Code Issues Projects Releases Wiki Activity

docs: update introduction

Browse Source
This commit is contained in:
Thomas Heartman 2022-04-19 09:57:10 +02:00
parent 4b8c3c3949
commit 54bfe7323d
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/docs/reference/api-tokens-and-client-keys.mdx
View File

@ -2,7 +2,13 @@
title: API tokens and client keys title: API tokens and client keys
--- ---
Unleash has a number of tokens/keys that all have slightly different use cases. Here's the list of all of them: For Unleash to be of any use, it requires at least a server and a [consuming client](../sdks/index.md).
More advanced use cases may call for multiple clients, automated feature toggle updates, the [Unleash proxy](../sdks/unleash-proxy.md) and [Unleash proxy clients](../sdks/index.md#front-end-sdks), and more. To facilitate communication between all these moving parts, Unleash uses a system of API tokens and client keys, all with a specific purpose in mind.
This document details the three kinds of tokens and keys that you will need to fully connect any Unleash system:
- [Admin tokens](#admin-tokens) for updating resources in Unleash
- [Client tokens](#client-tokens) for connecting server-side client SDKs and the Unleash proxy to the Unleash server
- [Proxy client keys](#proxy-client-keys) for connecting proxy client SDKs to the Unleash proxy.
## API tokens ## API tokens