- Upload stores the local bytes once in your organization’s library.
- Push creates a delivery from that library file to a phone.
Upload and push
- Dashboard
- CLI
- Python SDK
- Go SDK
- REST API
Open Files for your
organization and choose Upload Files, drag files onto the page, or upload
from the Files tool during a workflow or session.During an active session, open the Files tool, select a library file,
and choose Send. The delivery reports progress and reaches
delivered
or failed after the phone responds.dispatching to dispatched, then to delivered
or failed. The phone may also report bytes_transferred while a delivery is
in progress.
Download a file
Only a ready file has adownload_url. The URL is short-lived and needs no
Axilio authentication header.
- Dashboard
- CLI
- Python SDK
- Go SDK
- REST API
On Files, choose the
download action on a ready file. Selecting a preview opens the original in a
new tab.
Rename an uploaded file
Onlysource=upload files can be renamed. A capture keeps the filename that
the phone reported because it is part of the capture’s provenance. Renaming is
metadata-only: existing URLs still work, and earlier deliveries retain the
name they used at push time.
- Dashboard
- Python SDK
- Go SDK
- REST API
On Files, use the rename
action beside an uploaded filename. Captured filenames have no rename
action.
axilio files upload <path> --filename <name> or use one of the
rename interfaces above.
Delete
Deleting a file removes it from the library and frees its quota. Copies already on phones are not touched, whether the file was pushed to a phone or captured from one. Removing a file from a phone is a separate operation and is not available yet.- Dashboard
- CLI
- Python SDK
- Go SDK
- REST API
Open Files and choose
the delete action on the file. The confirmation shows how many phones were
sent a copy; those copies stay on the phones.
Deleting a captured file removes the library copy only. The media stays on
the phone it was captured from, and on any phone it was later pushed to.