Prerequisites
- A running Zipline instance
- ShareX installed on your Windows machine
- A Zipline user account with an API token
Getting Your API Token
The generated config file includes your API token and all necessary upload settings. Keep this file secure as it contains authentication credentials.
Manual Configuration
If you prefer to configure ShareX manually, follow these steps:File Upload Configuration
URL Shortener Configuration
Advanced Options
Zipline supports additional upload options through custom headers:Custom Headers
Available Headers
| Header | Description | Example Values |
|---|---|---|
x-zipline-deletes-at | Set file expiration | 24h, 7d, never, date=2024-12-31 |
x-zipline-format | Filename format | random, uuid, date, name, gfycat |
x-zipline-image-compression-percent | Image compression quality (0-100) | 80, 60, 90 |
x-zipline-max-views | Maximum views before deletion | 1, 10, 100 |
x-zipline-password | Password protect the file | Any string |
x-zipline-original-name | Keep original filename | true, false |
x-zipline-domain | Custom return domain | cdn.example.com |
XShare Compatibility (Android)
If you’re using the XShare app on Android, enable the compatibility option in Zipline’s generator settings:Troubleshooting
Upload fails with 401 Unauthorized
- Verify your API token is correct
- Check that the
authorizationheader is set properly - Ensure your Zipline user account is active
Upload fails with 413 Payload Too Large
- Check your file size limits in Zipline configuration
- Verify your user quota hasn’t been exceeded
- Contact your Zipline administrator for increased limits
Response URL is not captured
For file uploads, ensure the URL pattern is set to:- ShareX:
{json:files[0].url} - XShare:
$json:files[0].url$
{json:url}
Next Steps
API Documentation
Learn more about the upload API endpoints
Flameshot Integration
Set up Flameshot on Linux