Skip to content

Commit 7ae133b

Browse files
authored
Merge pull request #4174 from segmentio/spencerattick-patch-2
add info about using base64 encoding
2 parents d51ad42 + 46313dd commit 7ae133b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/profiles/profile-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -163,7 +163,7 @@ The Profile API uses basic authentication for authorization — with the **Acces
163163

164164
You can create your Access Secret in your Profiles Settings page. Segment recommends that you name your tokens with the name of your app and its environment, such as `marketing_site/production`. Access tokens are shown once — you won't be able to see it again. In the event of a security incident, you can revoke and cycle the access token.
165165

166-
When you make requests to the Profile API, use the Access Token as the basic authentication username and keep the password blank.
166+
When you make requests to the Profile API, use the Access Token as the basic authentication username and keep the password blank. Base64 is a requirement for authentication. If you use a tool like Postman, or if you use the `-u` flag in a cURL request, this encoding occurs automatically. Otherwise, you'll need to use Base64 to manually encode your Access Token.
167167

168168
```bash
169169
curl https://profiles.segment.com/v1/spaces/<space_id>/collections/users/profiles

0 commit comments

Comments
 (0)