diff --git a/websitev2/docs/api/admin/addons.md b/websitev2/docs/api/admin/addons.md index 6747e091a9..1e68a31e08 100644 --- a/websitev2/docs/api/admin/addons.md +++ b/websitev2/docs/api/admin/addons.md @@ -3,7 +3,7 @@ id: addons title: /api/admin/addons --- -> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](../../user_guide/api-token) and add an Authorization header using the token. +> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](/user_guide/api-token) and add an Authorization header using the token. ### List addons and providers {#list-addons-and-providers} diff --git a/websitev2/docs/api/admin/context.md b/websitev2/docs/api/admin/context.md index b0384ca7a6..ab84c980b4 100644 --- a/websitev2/docs/api/admin/context.md +++ b/websitev2/docs/api/admin/context.md @@ -3,7 +3,7 @@ id: context title: /api/admin/context --- -> The context feature is only available as part of Unleash Enterprise. In order to access the API programmatically you need to make sure you [obtain a API token](../../user_guide/api-token) with admin permissions. +> The context feature is only available as part of Unleash Enterprise. In order to access the API programmatically you need to make sure you [obtain a API token](/user_guide/api-token) with admin permissions. ### List context fields defined in Unleash {#list-context-fields-defined-in-unleash} diff --git a/websitev2/docs/api/admin/events-api.md b/websitev2/docs/api/admin/events-api.md index 3fbdd1f61d..ae1cdde09b 100644 --- a/websitev2/docs/api/admin/events-api.md +++ b/websitev2/docs/api/admin/events-api.md @@ -3,7 +3,7 @@ id: events title: /api/admin/events --- -> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](../../user_guide/api-token) and add an Authorization header using the token. +> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](/user_guide/api-token) and add an Authorization header using the token. # Events API diff --git a/websitev2/docs/api/admin/feature-toggles-api.md b/websitev2/docs/api/admin/feature-toggles-api.md index 4f7239ce7e..04be2b504d 100644 --- a/websitev2/docs/api/admin/feature-toggles-api.md +++ b/websitev2/docs/api/admin/feature-toggles-api.md @@ -3,7 +3,7 @@ id: features title: /api/admin/features --- -> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](../../user_guide/api-token) and add an Authorization header using the token. +> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](/user_guide/api-token) and add an Authorization header using the token. ### Fetching Feature Toggles {#fetching-feature-toggles} diff --git a/websitev2/docs/api/admin/feature-toggles-archive-api.md b/websitev2/docs/api/admin/feature-toggles-archive-api.md index d19509ac2c..24a673e48c 100644 --- a/websitev2/docs/api/admin/feature-toggles-archive-api.md +++ b/websitev2/docs/api/admin/feature-toggles-archive-api.md @@ -3,7 +3,7 @@ id: features-archive title: /api/admin/archive --- -> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](../../user_guide/api-token) and add an Authorization header using the token. +> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](/user_guide/api-token) and add an Authorization header using the token. ### Fetch archived toggles {#fetch-archived-toggles} diff --git a/websitev2/docs/api/admin/feature-types-api.md b/websitev2/docs/api/admin/feature-types-api.md index 019ccb475f..44a887bedf 100644 --- a/websitev2/docs/api/admin/feature-types-api.md +++ b/websitev2/docs/api/admin/feature-types-api.md @@ -3,7 +3,7 @@ id: feature-types title: /api/admin/feature-types --- -> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](../../user_guide/api-token) and add an Authorization header using the token. +> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](/user_guide/api-token) and add an Authorization header using the token. # Feature Types API diff --git a/websitev2/docs/api/admin/metrics-api.md b/websitev2/docs/api/admin/metrics-api.md index c51287091c..d432ba6fc4 100644 --- a/websitev2/docs/api/admin/metrics-api.md +++ b/websitev2/docs/api/admin/metrics-api.md @@ -3,7 +3,7 @@ id: metrics title: /api/admin/metrics --- -> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](../../user_guide/api-token) and add an Authorization header using the token. +> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](/user_guide/api-token) and add an Authorization header using the token. # This document describes the metrics endpoint for admin ui diff --git a/websitev2/docs/api/admin/project.md b/websitev2/docs/api/admin/project.md index aa6b6c7aca..aefb788b7b 100644 --- a/websitev2/docs/api/admin/project.md +++ b/websitev2/docs/api/admin/project.md @@ -3,7 +3,7 @@ id: projects title: /api/admin/projects --- -> The context feature is only available as part of Unleash Enterprise. In order to access the API programmatically you need to make sure you [obtain an API token](../../user_guide/api-token) with admin permissions. +> The context feature is only available as part of Unleash Enterprise. In order to access the API programmatically you need to make sure you [obtain an API token](/user_guide/api-token) with admin permissions. ### List projects in Unleash {#list-projects-in-unleash} diff --git a/websitev2/docs/api/admin/state-api.md b/websitev2/docs/api/admin/state-api.md index 3b42d59da8..39cf473592 100644 --- a/websitev2/docs/api/admin/state-api.md +++ b/websitev2/docs/api/admin/state-api.md @@ -3,7 +3,7 @@ id: state title: /api/admin/state --- -> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](../../user_guide/api-token) and add an Authorization header using the token. +> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](/user_guide/api-token) and add an Authorization header using the token. ### Export Feature Toggles & Strategies {#export-feature-toggles--strategies} diff --git a/websitev2/docs/api/admin/strategies-api.md b/websitev2/docs/api/admin/strategies-api.md index e708d08f21..2dec9371c6 100644 --- a/websitev2/docs/api/admin/strategies-api.md +++ b/websitev2/docs/api/admin/strategies-api.md @@ -3,7 +3,7 @@ id: strategies title: /api/admin/strategies --- -> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](../../user_guide/api-token) and add an Authorization header using the token. +> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](/user_guide/api-token) and add an Authorization header using the token. ### Fetch Strategies {#fetch-strategies} diff --git a/websitev2/docs/api/admin/tags-api.md b/websitev2/docs/api/admin/tags-api.md index 2ba4c14853..c076f5f5fb 100644 --- a/websitev2/docs/api/admin/tags-api.md +++ b/websitev2/docs/api/admin/tags-api.md @@ -3,7 +3,7 @@ id: tags title: /api/admin/tags --- -> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](../../user_guide/api-token) and add an Authorization header using the token. +> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](/user_guide/api-token) and add an Authorization header using the token. ### Create a new tag {#create-a-new-tag} diff --git a/websitev2/docs/api/admin/user-admin.md b/websitev2/docs/api/admin/user-admin.md index 959c062915..6c495974b8 100644 --- a/websitev2/docs/api/admin/user-admin.md +++ b/websitev2/docs/api/admin/user-admin.md @@ -3,7 +3,7 @@ id: user-admin title: /api/admin/user-admin --- -> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](../../user_guide/api-token) and add an Authorization header using the token. +> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](/user_guide/api-token) and add an Authorization header using the token. ### List all users {#list-all-users} diff --git a/websitev2/docs/api/client/metrics-api.md b/websitev2/docs/api/client/metrics-api.md index 3882485b42..3e67ca3909 100644 --- a/websitev2/docs/api/client/metrics-api.md +++ b/websitev2/docs/api/client/metrics-api.md @@ -3,7 +3,7 @@ id: metrics title: /api/client/metrics --- -> In order to access the client API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create a CLIENT token](../../user_guide/api-token) and add an Authorization header using the token. +> In order to access the client API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create a CLIENT token](/user_guide/api-token) and add an Authorization header using the token. ### Send metrics {#send-metrics} diff --git a/websitev2/docs/api/client/register-api.md b/websitev2/docs/api/client/register-api.md index 048702a0dd..a4842a52e6 100644 --- a/websitev2/docs/api/client/register-api.md +++ b/websitev2/docs/api/client/register-api.md @@ -3,7 +3,7 @@ id: register title: /api/client/register --- -> In order to access the client API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create a CLIENT token](../../user_guide/api-token) and add an Authorization header using the token. +> In order to access the client API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create a CLIENT token](/user_guide/api-token) and add an Authorization header using the token. ### Client registration {#client-registration}