> ## Documentation Index > Fetch the complete documentation index at: https://docs.gmicloud.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get live Template Build logs > Queries the underlying provider's Build log API. GMI does not persist these logs. Logs are filtered and paged by the GMI adapter because the provider returns a complete log collection. ## OpenAPI ````yaml /api-spec/sandbox_api.yaml get /templates/{template_id}/builds/{id}/logs openapi: 3.0.3 info: title: GMI Sandbox API description: >- REST API for GMI Sandbox: create isolated execution environments from templates, manage their lifecycle on the control plane, and run commands or transfer files through each sandbox's own data plane. contact: name: GMI Cloud Support email: support@gmicloud.ai version: '2.0' servers: - url: https://console.gmicloud.ai/api/v2 description: Control plane security: - bearerAuth: [] tags: - name: Sandbox description: | Sandbox instance lifecycle management (Sandbox v2, /api/v2/sandboxes) - name: SandboxTemplate description: Sandbox template management (Sandbox v2, `/api/v2/templates`) - name: Sandbox-Exec description: > Sandbox execution data plane (accessed via the sandbox host and sandbox access token). These endpoints are not under the control plane's `/api/v2` path; clients connect directly to `https://{sandbox_key}.{domain}` and authenticate with `X-Access-Token`. - name: Sandbox-Files description: > Sandbox file data plane (`/files`). **These endpoints are not under `/api/v2`** and do not use `Authorization: Bearer`: they are served by the sandbox's own data-plane entry point — clients connect directly to `https://{sandbox_key}.{domain}` and authenticate with `X-Access-Token`. `{sandbox_key}` is the `sandbox_key` returned by the create/connect endpoints, used for data-plane host addressing. `{domain}` and `X-Access-Token` are the `domain` and `sandbox_access_token` from the same responses — no extra endpoint is needed to obtain them. This split is not historical baggage but the nature of a data plane: file transfer is long-lived, high-volume, and addressed per sandbox, differing from the control plane's short requests in both capacity model and failure domain, so they do not share an entry point. **One unified abstraction.** The same contract is served by two backend kinds (an in-sandbox file service / a data-center data-plane proxy); clients need not — and cannot — tell them apart. The cost is that the contract is their intersection: `Content-Length` on download and resumable download (`Range`/`206`) are **optional capabilities** that vary by data center, and clients must work correctly when they are absent. See the per-operation notes below. paths: /templates/{template_id}/builds/{id}/logs: parameters: - $ref: '#/components/parameters/TemplateBuildTemplateIdPathParam' - $ref: '#/components/parameters/BuildIdPathParam' get: tags: - SandboxTemplate summary: Get live Template Build logs description: > Queries the underlying provider's Build log API. GMI does not persist these logs. Logs are filtered and paged by the GMI adapter because the provider returns a complete log collection. operationId: getTemplateBuildLogs parameters: - name: offset in: query description: Zero-based normalized log entry offset. schema: type: integer format: int64 minimum: 0 default: 0 - name: limit in: query description: Maximum number of log entries to return. schema: type: integer minimum: 1 maximum: 100 default: 100 - name: level in: query description: Optional normalized log level filter. schema: type: string enum: - debug - info - warn - error responses: '200': description: Build logs were returned successfully. content: application/json: schema: $ref: '#/components/schemas/BuildLogPageResponse' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '410': $ref: '#/components/responses/ArtifactReclaimed' '500': $ref: '#/components/responses/InternalError' '502': $ref: '#/components/responses/ProviderError' components: parameters: TemplateBuildTemplateIdPathParam: name: template_id in: path required: true description: Owning GMI Template identifier. schema: type: string format: uuid BuildIdPathParam: name: id in: path required: true description: GMI Template Build identifier. schema: type: string format: uuid schemas: BuildLogPageResponse: type: object additionalProperties: false required: - request_id - data properties: request_id: type: string description: HTTP request correlation identifier. data: $ref: '#/components/schemas/BuildLogPage' BuildLogPage: type: object additionalProperties: false required: - entries - next_offset - has_more properties: entries: type: array items: $ref: '#/components/schemas/BuildLogEntry' next_offset: type: integer format: int64 minimum: 0 description: Offset to use for the next request. has_more: type: boolean description: Whether more provider log entries are currently available. ErrorResponse: type: object required: - code - message - request_id properties: code: type: string description: Machine-readable business error code example: Resource.QuotaExceeded message: type: string description: Human-readable error description example: The resource quota is not enough. request_id: type: string description: Tracing ID example: req-xxxx details: type: object description: Field-level error details additionalProperties: true BuildLogEntry: type: object additionalProperties: false required: - offset - level - message properties: offset: type: integer format: int64 minimum: 0 description: Normalized zero-based log entry offset. timestamp: type: string format: date-time nullable: true description: Provider-reported log time in UTC when available. level: type: string enum: - debug - info - warn - error description: Normalized log level. message: type: string description: Sanitized provider log message. responses: BadRequest: description: Invalid request parameters content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: code: Parameter.Invalid message: Invalid request parameters request_id: req-xxxx Unauthorized: description: Unauthenticated content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: code: Auth.Unauthorized message: Authentication required request_id: req-xxxx Forbidden: description: The caller cannot access the organization-scoped resource. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' NotFound: description: Resource not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: code: Resource.NotFound message: The requested resource was not found request_id: req-xxxx ArtifactReclaimed: description: The provider artifact and its live logs are no longer available. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' InternalError: description: Internal server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: code: Internal.ServerError message: An internal server error occurred request_id: req-xxxx ProviderError: description: The selected Sandbox provider is unavailable or returned an error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: bearerAuth: type: http scheme: bearer description: > API Key or Access Token, always sent as `Authorization: Bearer `. The gateway recognizes the token type automatically. ````