Skip to main content

Get Token

GET /api/user/token

Retrieve your encrypted API token for uploading files and accessing the API.

Request

curl -X GET https://your-zipline.com/api/user/token \
  -H "Authorization: YOUR_TOKEN" \
  -H "Cookie: zipline_token=YOUR_SESSION_TOKEN"

Response

token
string
Encrypted API token string. Use this token in the Authorization header for API requests.
Example Response
{
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
}
The token is encrypted using the server’s secret key. This is the token you should use for ShareX, uploaders, and other integrations.

Reset Token

PATCH /api/user/token

Generate a new API token. Warning: This will invalidate your existing token and break any integrations using it.

Request

curl -X PATCH https://your-zipline.com/api/user/token \
  -H "Authorization: YOUR_TOKEN" \
  -H "Cookie: zipline_token=YOUR_SESSION_TOKEN"

Response

user
object
Updated user object with the new token
token
string
Encrypted token string for API authentication
Example Response
{
  "user": {
    "id": "clxxx123456789",
    "username": "john_doe",
    "role": "USER",
    "token": "abc123xyz..."
  },
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
}

Rate Limiting

This endpoint is rate-limited to 1 request per second to prevent token cycling abuse.
Resetting your token will immediately invalidate the old token. You’ll need to update the token in:
  • ShareX configurations
  • Browser extensions
  • CLI tools
  • Any other integrations

Build docs developers (and LLMs) love