summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorTimothy Andrew <mail@timothyandrew.net>2016-05-11 10:16:23 +0530
committerTimothy Andrew <mail@timothyandrew.net>2016-05-11 10:16:23 +0530
commitd915e7d5cad99b8971e65d30accc8bc7a05fecbc (patch)
tree0583e9d36fb2d38101737d0a891ac29b7d87c373 /doc
parent2e9742997ddbfaeff350eb5334b7f641a779550c (diff)
downloadgitlab-ce-d915e7d5cad99b8971e65d30accc8bc7a05fecbc.tar.gz
Reuse the private token param and header for personal access tokens.
- https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3749#note_11626427 - Personal access tokens are still a separate entity as far as the codebase is concerned - they just happen to use the same entry point as private tokens. - Update tests and documentation to reflect this change
Diffstat (limited to 'doc')
-rw-r--r--doc/api/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/api/README.md b/doc/api/README.md
index 0e9dc7acfed..276816b2807 100644
--- a/doc/api/README.md
+++ b/doc/api/README.md
@@ -77,8 +77,8 @@ You can create as many personal access tokens as you like from your GitLab
profile (`/profile/personal_access_tokens`); perhaps one for each application
that needs access to the GitLab API.
-Once you have your token, pass it to the API using either the `personal_access_token`
-parameter or the `PERSONAL-ACCESS-TOKEN` header.
+Once you have your token, pass it to the API using either the `private_token`
+parameter or the `PRIVATE-TOKEN` header.
## Basic Usage