Skip to content

Update Profile API Guidance on Escape Characters #6460

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 7, 2024
Merged

Update Profile API Guidance on Escape Characters #6460

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
62d1a1f
Update profile-api.md Escape Characters
lizkane222 Apr 29, 2024
5dc505d
External links and cleanup
pwseg May 7, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/unify/profile-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,8 @@ Your access token enables you to call the Profile API and access customer data.
> warning ""
> To query phone numbers that contain a plus sign (`+`), insert the escape characters `%2B` in place of the plus sign.
> For example, if a `phone_number` identifier has the value `+5555550123`, enter `phone_number:%2B5555550123` in your query.
>
> If the field you're using within the Profile API endpoint contains a value with a non-alphanumeric character, then the Profile API may respond with `500` error. In this case, see [W3's ASCII Encoding Refernece](https://www.w3schools.com/tags/ref_urlencode.ASP#:~:text=ASCII%20Encoding%20Reference,%25C3%25BF){:target="_blank"}, which lists the escape characters you can use to replace the non-alphanumeric character in the Profile API endpoint so that the Profile API will respond with a `200 Success`.

### Query the user's event traits

Expand Down