Get the document or image produced by a completed render task.
Note that the PDF or image result will be a binary blob in the HTTP response, as indicated by the Content-Type in the response headers. This may require specialized (or at least different) handling than text responses such as JSON. You may need to tell your HTTP client that the response is binary so that it does not attempt to parse the binary data as text.
If the render task exists but has not finished rendering the results, the response HTTP status will be 202 Accepted, the response body will be empty, and the response will have a Retry-After header indicating that the caller should repeat the request at a later time.
Returns 404 if the render task cannot be found, if the cached result has expired, or if the caller does not have permission to view the results.
For detailed information about the status of the render task, use Render Task. Polling loops waiting for completion of a render task would be better served by polling render_task(id) until the task status reaches completion (or error) instead of polling render_task_results(id) alone.
Request
Response
200: Document or image
202: Accepted
400: Bad Request
404: Not Found
429: Too Many Requests
Examples
Python
Ruby
| https://github.com/looker-open-source/sdk-codegen/blob/main/examples/ruby/render_look_png.rb |
TypeScript
| https://github.com/looker-open-source/sdk-codegen/blob/main/examples/typescript/utils.ts |
Kotlin
| https://github.com/looker-open-source/sdk-codegen/blob/main/kotlin/src/test/KotlinExample.kt |