fshy

Home / Storage

Cisco Webex — Messages API file attachments

developer.webex.com/docs/basics#message-attachmentsMessagingstorage/cisco-webex-messages-api-file-attachmentsJSONcomparereport an errorprovider JSON

Free allowance
No storage quota published.
Verdict
fails: egressdata cannot be read back out at a usable rate or price
Cost
free tier
Identity
institution?placeholder, not evidence; card unknown, phone unknown
Binding limit
noneno named constraint binds
Evidence
inferred2 sources; reasoned from other evidence
Freshness
stale on 2026-11-21checked 2026-10-21 (inherited); stale on 2026-11-21
Free tierNo storage quota published. Per-attachment cap is the only hard number: 'Message attachments are limited to 100MB each.'
unit mixed; metered on stored-bytes
Pricenone stated
Identityinstitution (inferred, not read) not published
EgressNo per-GB egress charge found, but files are fetched by authenticated API call or a short-lived download URL tied to the message — not an anonymous CDN path.
Per-object capnot stated
RetentionRetention is governed by the org's retention policy (license-dependent); free-tier spaces are not a documented permanent store
Interfacerest rest
Toolingwebexteamssdk / webex-python-sdk; POST /v1/messages with multipart files, GET /v1/contents/{id}. Room Tabs API can attach a persistent URL to a space but does not store bytes.
Composes with100 MB/attachment x unlimited messages in a space is genuinely large in principle, but free Webex accounts have message-retention limits and the org pays per user beyond the free tier.
ReliabilityRetention is policy-driven rather than fixed, so an admin policy change or license lapse can remove content without any API-visible warning. Unverified for the free tier specifically — blocked from the retention help page.
Parsed numbers
  • has-free-tier 1
Evidence 2
datesourcewhat it proved
2026-10-21developer.webex.com/docs/basics#message-attachmentsread live: 'Message attachments are limited to 100MB each.'
2026-10-21help.webex.com/en-us/article/8c1lzx/Manage-retention-policieunverified: blocked by challenge (no retention number obtained)
More fields 1
dead end{"failure_class": "quota","why": "No storage quota published. Per-attachment cap is the only hard number: 'Message attachments are limited to 100MB each.'","retry_when": null,"first_recorded": "2026-10-21"}
Unknown values 3
  • per object cap notes: the field may be stated in a source that was not read
  • per object cap stated: the field may be stated in a source that was not read
  • retention notes: the field may be stated in a source that was not read