Skip to content

UID2-6366: Add curl example to token/refresh #1085

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
samin-ttd merged 2 commits into from
Oct 19, 2026
Merged

UID2-6366: Add curl example to token/refresh #1085

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a7de96a
UID2-6366: Add curl example to token/refresh
samin-ttd Oct 19, 2026
c324964
UID2-6980: Real looking refresh token
samin-ttd Oct 19, 2026
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
20 changes: 19 additions & 1 deletion docs/endpoints/post-token-refresh.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,25 @@ Using either of the following parameters in a [POST /token/generate](post-t

### Request example

For details, and code examples in different programming languages, see [Encrypting requests and decrypting responses](../getting-started/gs-encryption-decryption.md).
The following example refreshes a token with `curl`. Replace `{environment}` with the base URL for your environment, and `{refresh_token}` with the `refresh_token` value from the previous [POST /token/generate](post-token-generate.md) or `POST /token/refresh` response:

```sh
curl -X POST '{environment}/v2/token/refresh' -d '{refresh_token}'
```

For example, using the integration environment:

```sh
curl -X POST 'https://operator-integ.uidapi.com/v2/token/refresh' -d 'AAAAAGYzgUszke2sV9CxXnxyFfUU+KDCJUCXNbj1/FVcCjvR7K07jYaWe44wxM6SOTwG7WQB4XfIcquMqH57iHUnAu1zacYf9g58BtbhKCYWTwrdpB0fSqTANBXOYy+yBnl6tLRwVv32LqRCj76D8meO4tw+MKlUAc2EoFzFNPSfZLpA3Jk4q68vH6VJH/WIuu1tulrVm5J8RZAZnmTlEcsPdjoOC6X4w3aAwiwtbeGw7yOO0immpVoC5KaXnT9olRPTlrt8F9SvebLIcqkYhvRMPpl1S89yeneyGo++RnD9qSHIrfu9To3VwYW018QuvyA15uv4No4BoAzyPuHqzQ8gAs6csWwZ7VwfYD7DSJXlQiIpwzjA2Hl8mgg/5fcXwKEJ'
```

Notes:

- The request needs no `Authorization` header (API key) and no encrypted request envelope. The POST body is the refresh token only, not JSON.
- A successful response (HTTP status code 200) is a base64-encoded encrypted string, so `curl` cannot show you its contents. To decrypt it, use the `refresh_response_key` value that was returned with the refresh token. See [Encrypting requests and decrypting responses](../getting-started/gs-encryption-decryption.md).
- An error response (for example, HTTP status code 400) is not encrypted, so `curl` shows the error. A 200 status code confirms that the operator is reachable and accepted the refresh token, even if you do not decrypt the response.

For code examples in different programming languages, see [Encrypting requests and decrypting responses](../getting-started/gs-encryption-decryption.md).

## Decrypted JSON response format

Expand Down
Loading