pc-style Uploading with up!link
Use curl only. Never print or commit UPLINK_API_KEY. If UPLINK_API_KEY is missing, ask the user to configure it rather than guessing.
Keys shaped uplink_<host>_<secret> embed the server address. Derive the base URL first:
rest="${UPLINK_API_KEY#uplink_}"
base="${UPLINK_BASE_URL:-https://${rest%_*}}"
If the key lacks the uplink_ prefix, UPLINK_BASE_URL is required instead; ask the user for it when unset.
Upload a local file, defaulting to a temporary link:
curl -sS --fail-with-body \
"${base%/}/api/upload" \
-H "Authorization: Bearer $UPLINK_API_KEY" \
-F "file=@<path>" \
-F "permanent=false"
Use permanent=true only when requested. Add short=true for a seven-day short link, plus shortName=<name> for a custom path. Return the relevant temporaryUrl, permanentUrl, or shortUrl, not the full response.
For a file already online, call POST ${base%/}/api/ingest-url with JSON containing url, filename, and permanent. For direct client uploads, call POST /api/upload-url, then PUT the bytes to its returned uploadUrl without the API key.
Treat 401 as bad configuration, 403 as an expired or invalid signed URL, 409 as a duplicate custom path, and 413 as a reason to use multipart instead of JSON.