You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/integrations/rest-api.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -682,13 +682,13 @@ It is possible to provision authentication tokens for other users via the REST A
682
682
683
683
### Authenticating to the API
684
684
685
-
An authentication token is included with a request in its `Authorization` header. The format of the header value depends on the version of token in use. v2 tokens use the following form, concatenating the token's key and plaintext value with a period:
685
+
An authentication token is included with a request in its `Authorization` header. The format of the header value depends on the version of token in use. v2 tokens use the following form, concatenating the token's prefix (`nbt_`) and key with its plaintext value, separated by a period:
686
686
687
687
```
688
-
Authorization: Bearer <key>.<token>
688
+
Authorization: Bearer nbt_<key>.<token>
689
689
```
690
690
691
-
v1 tokens use the prefix `Token` rather than `Bearer`, and include only the token plaintext. (v1 tokens do not have a key.)
691
+
Legacy v1 tokens use the prefix `Token` rather than `Bearer`, and include only the token plaintext. (v1 tokens do not have a key.)
692
692
693
693
```
694
694
Authorization: Token <token>
@@ -697,7 +697,7 @@ Authorization: Token <token>
697
697
Below is an example REST API request utilizing a v2 token.
0 commit comments