WEBSERVICE in Collabora Office: Retrieve Web Response Text for a Worksheet
Understand Collabora WEBSERVICE’s URI input, separate retrieval from parsing, and preserve response snapshots without inventing stable live outputs or authentication support.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: =WEBSERVICE(URI) retrieves web content from the supplied URI. The expected content depends on the remote response; the function does not promise a fixed table, a particular XML field, or an unchanging result.
Syntax and the single argument
=WEBSERVICE(URI)
URI is required text identifying the web service. A literal is quoted; a cell reference can supply the text. The dedicated section documents no separate headers, authentication, request-body, HTTP-method, timeout, or refresh-interval arguments.
Do not add parameters from another product’s web-fetch function. Also do not place passwords or access tokens in a URL to work around missing authentication features; URLs can be exposed in workbooks, logs, or shared files.
The vendor’s documented feed example
The source gives a Document Foundation recent-changes RSS request. Written with the explicit HTTPS scheme identified by its explanation:
=WEBSERVICE("https://wiki.documentfoundation.org/api.php?hidebots=1&days=7&limit=50&action=feedrecentchanges&feedformat=rss")
The documented purpose is to return that resource’s web content. No current response, endpoint availability, or native network request was verified for this guide. The feed is time-dependent, so a fixed article list or timestamp would be an invented expected output.
The URL itself is not the response. A successful retrieval should supply response content for further inspection, while a visible URL string alone does not prove a fetch occurred.
Reproducible interpretation with a controlled response fixture
To audit downstream formulas without relying on the network, put the exact synthetic response text Ready in A2. Then =LEN(A2) has independent result 5, and =LEFT(A2;3) has independent result Rea.
If a trusted test endpoint under your control is configured to return exactly those five characters, the documentation-based retrieval target would be Ready, and the same checks would apply. This guide does not provide or claim to have deployed such an endpoint. The fixed text fixture is a parsing control, not a fake WEBSERVICE execution.
LEN and LEFT can inspect a retained response. A length or prefix check alone cannot validate an entire response or prove that a service request succeeded.
Advanced application: separate the three stages
Build a worksheet with distinct places for the URI, the retrieved content, and the parsed result. For example, A5 can contain the trusted URI, B5 can contain =WEBSERVICE(A5), and another cell can extract a value from B5 only after the response format is known.
For XML, the vendor links FILTERXML as a related function and demonstrates extracting //lastBuildDate in its FILTERXML example. JSON or HTML requires its own supported parsing approach; changing a URL does not automatically turn arbitrary content into a spreadsheet table.
Keep raw response text during troubleshooting so a parsing error can be distinguished from an authentication page, rate-limit message, changed schema, or unavailable service. Those are possible external conditions, not verified outcomes for the example endpoint.
Advanced use: preserve a dated snapshot
If a report must be reproducible, preserve the actual response text, retrieval time, URI, and the formulas used to interpret it. A live formula is not a permanent record of yesterday’s response.
When copying a snapshot, verify that the destination contains the value rather than a formula that may fetch again. Avoid sharing sensitive response content or account-specific URLs unintentionally. A public example feed does not authorize sending private workbook data to arbitrary services.
Errors, refresh, and compatibility limits
The dedicated page does not state a complete refresh schedule, caching policy, size limit, supported authentication methods, error-code table, or network-permission behavior. This guide does not borrow those details from Excel or assume every Collabora deployment has the same network access.
Check the URI, its trustworthiness, the actual response type, and any application prompts. Do not weaken security settings merely to make a demonstration work. The function’s availability in desktop help is not proof of successful runtime access to a particular site.
The vendor identifies WEBSERVICE as outside OpenDocument 1.3 OpenFormula with namespace COM.MICROSOFT.WEBSERVICE. That name does not certify compatibility, a service-level guarantee, or current support in an online/mobile deployment. All fixed outputs in this guide belong to explicitly labeled local-text controls.
Availability and verification
The exact function is documented in Collabora Office 26.04 desktop help, retrieved and reviewed on October 17, 2026. This establishes a documentation scope, not the first release that introduced the function or the last version in which it works; those versions and any retirement date remain unestablished. Collabora Online and mobile support are not inferred from desktop help, nor is behavior in another spreadsheet product.
The examples are documentation-based expectations with independent calculations. They have not been executed in Collabora Office. No application screenshot or native error/coercion certification is implied. Formulas use English function names and semicolon argument separators.
References
- Collabora Office 26.04: WEBSERVICE (checked October 17, 2026).
- Editorial testing standards.