/api/user/token

Get a valid token or refresh the underlying key that generates valid tokens.

How do tokens on Zipline work? You may notice that every time you "copy" a token from the dashboard, it is actually a new and different token. This is because Zipline generates this token dynamically based on the current time + a underlying secret key which is then encrypted using the CORE_SECRET environment variable. Refreshing a token will simply update the underlying secret key, which will then invalidate all previously generated tokens.

Info

This endpoint requires authentication.

GET
Request

Retrieve an encrypted token.

Response

Status: 200 OK

Content-Type: application/json

PropertyTypeDescription
tokenstringThe encrypted API token for the authenticated user.

PATCH
Request

Update the underlying secret key used to generate tokens.

Response

Status: 200 OK

Content-Type: application/json

Returns the same response as the POST /api/auth/login endpoint.



Last updated: 5/28/2025
Edit this page on GitHub