Open a share link, unlock a protected share, or request a signed download URL.
Start with the share address. Protection adds a second credential but does not change the public /d/{shortId} address.
Open https://beecargo.net/d/{shortId}. That full share URL is the handoff. Recipients should not need a separate code-entry step.
If the share asks for a code, enter the separate 6-character unlock code supplied by the sender. If the sender supplied a /h/{token} delivery link, open it instead; the token authorizes the share without typing the code.
Machine downloads wait for the safety check to finish before a signed URL is issued.
Check unlockRequired in file or share metadata. POST /downloads/unlock accepts { shortId|fileId, unlockCode } or { handoffToken } and returns a short-lived unlockToken. Pass that token to the download endpoint, or pass the unlock code or handoff token directly.
Endpoint
Authentication
No API key needed. If the share is protected, pass unlockCode, unlockToken, or handoffToken. Priced shares need purchaseToken (or owner auth).
Request examples
# Get download URL (unprotected)
curl https://api.beecargo.net/files/download/550e8400-e29b-41d4-a716-446655440000
# Protected share: unlock first, then download
curl -X POST https://api.beecargo.net/downloads/unlock \
-H "Content-Type: application/json" \
-d '{"shortId":"AbC123","unlockCode":"XyZ789"}'
curl "https://api.beecargo.net/files/download/550e8400-e29b-41d4-a716-446655440000?unlockCode=XyZ789"
# Download file directly
curl -L https://api.beecargo.net/files/download/550e8400-e29b-41d4-a716-446655440000 \
-o downloaded-file.pdfParameters
Usage notes
scanPending: true and retryAfterSeconds (about 15). Wait that long and try again, or wait for the file.ready webhook. Some clients also see errorCode: SCAN_PENDING.scanBlocked). Poll GET /files/share/{shortId} for scanStatus: pending, scanning, clean, or unavailable. Download only when it is clean.scanStatus. Use the share metadata route above for readiness.unlockRequired and paymentRequired / priceCents on GET /files/share/{shortId} or GET /files/info before downloadingpurchaseToken (owners with auth may skip payment). CLI: beecargo download FILE_ID ./out --purchase-token TOKEN.POST /downloads/unlock with { shortId|fileId, unlockCode } or { handoffToken } returns unlockToken for later download calls/h/{token} unlock without typing the code; GET /files/handoff/{token} returns the message and shortIdTool
Authentication
No API key required.
Parameters
Usage notes
fileId. When the share is protected, pass unlockCode, unlockToken, or handoffToken. Priced shares also need purchaseToken (or owner auth).scanPending: true and retryAfterSeconds (about 15). Wait and retry, or wait for the file.ready webhook. Some responses use errorCode: SCAN_PENDING.scanBlocked). Poll GET /files/share/{shortId} for scanStatus (pending, scanning, clean, unavailable). Download only when it is clean.beecargo_file_info does not include scanStatus. Use share metadata for readiness.unlockRequired and paymentRequired / priceCents with beecargo_file_info or GET /files/share/{shortId} before calling this tool.unlockRequired is true, the /d/{shortId} link alone is not enough to download.beecargo_purchase_checkout → send checkoutUrl → beecargo_purchase_claim → retry with purchaseToken. Or send the human to /d/{shortId}. CLI: beecargo download FILE_ID ./out --purchase-token TOKEN.Command
Authentication
Requires --key for owned files, or unlock / purchase credentials for protected or priced shares.
Usage notes
--unlock-code, --unlock-token, or --handoff-token for protected shares.--purchase-token from the paid claim flow (or download as the owner with --key).--sha256 verifies the digest after download.Command
Authentication
Requires --key or BEECARGO_API_KEY.
Usage notes
Endpoint
Authentication
Optional. You can send an API key in the Authorization header.
Request examples
# Get info for a single file
curl "https://api.beecargo.net/files/info?file_code=abc123"
# Get info for multiple files (comma-separated)
curl "https://api.beecargo.net/files/info?file_code=abc123,xyz789,def456"
# With API key authentication
curl "https://api.beecargo.net/files/info?file_code=abc123&key=YOUR_API_KEY"
# Or with Authorization header
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://api.beecargo.net/files/info?file_code=abc123,xyz789"Parameters
Response fields
Usage notes
status of 200 (found) or 404 (not found).result has its own status (200 or 404)"active" can be downloadedscanStatus. Poll GET /files/share/{shortId} before machine download.unlockRequired is true, GET /files/download/{fileId} needs unlockCode or unlockToken (or call POST /downloads/unlock with handoffToken from /h/{token})Tool
Authentication
API key optional.
Parameters
Usage notes
GET /files/info?file_code=… on the API.scanStatus. Poll GET /files/share/{shortId} before machine download.unlockRequired: true, call beecargo_get_download_url with unlockCode, unlockToken, or handoffToken. The share link alone is not enough to download.Command
Authentication
Optional --key when the file is owned.
Usage notes