> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/web-services-framework/download-api-responses-in-small-chunks.md). # Download API Responses in Small Chunks ## Description Some web API responses are quite long, and it is useful to have the client download the response in small pieces or resume a download if the download is interrupted; for example, when the Internet connection is unstable. **Used With:** This function is used with the WebServicesFramework in LogicNets v8.1+. ## Details LogicNets’ WebServicesFramework supports downloading a response in smaller chunks by passing the *HTTP Range* header (): ``` GET /yourcompany/yourapi/endpoint HTTP/1.1 Range: bytes=0-1000 Authorization: Basic **** Accept: */* ``` In this case, the response is not written back to the client directly, but the API returns a *202 Accepted* status response, *Content-Range* that contains the size of the actual response in bytes, *Accept-Ranges*, and a *Location* URL header you can use to retrieve the actual result. ``` HTTP/1.1 202 Accepted LN-STATUS: 202 Accepted Location: /yourcompany/async.lns?_asyncid=abc&_session=123 Content-Range: bytes */2000 Accept-Ranges: bytes ``` The client can start downloading the result by calling the *Location* URL multiple times for each chunk. **Chunk 1** ``` GET /yourcompany/async.lns?_asyncid=abc&_session=123 HTTP/1.1 Range: bytes=0-1000 ``` **Chunk 2** ``` GET /yourcompany/async.lns?_asyncid=abc&_session=123 HTTP/1.1 Range: bytes=1001-2000 ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/web-services-framework/download-api-responses-in-small-chunks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.