> ## Documentation Index > Fetch the complete documentation index at: https://docs.tastelabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Get submission result > Returns the unified result envelope for a submission, including the extracted design system and stored artifacts. Results stream in: while the job runs you may receive a `200` with a partial `design_system`, and before the first checkpoint lands you receive `409 NOT_READY`. Keep polling until `status` is `completed` or `failed`. Use `sections` to narrow `result.design_system` to the sections you actually read. The full document is large, and `assets` and `layout` are commonly most of it. ## OpenAPI ````yaml api-reference/openapi.json GET /design/submissions/{id}/result openapi: 3.1.0 info: title: Taste Engine Design API version: 1.0.0 description: >- Public REST API for the Taste Engine. Submit a URL, extract a structured design system from any website, search the brand corpus by aesthetic, and ground prompts in real brand profiles. All requests are authenticated with an API key sent in the `X-API-Key` header. Create one directly in the Engine dashboard at https://engine.tastelabs.com/app/api-keys. contact: name: Taste Engine Support email: support@thetaste.ai servers: - url: https://api.tastelabs.com description: Production security: - ApiKeyAuth: [] tags: - name: Account description: Identity of the authenticated API key holder. - name: Submissions description: >- Create and track extraction jobs, then retrieve the resulting design system. - name: Prompts description: Rewrite prompts grounded in an extracted brand profile. - name: Search description: >- Find brands in the curated corpus by describing an aesthetic, or by similarity to one of your own extractions. - name: Brand adherence description: >- Judge how well a page adheres to a reference site's brand: submit a pair of URLs, poll the job, then read the verdict. paths: /design/submissions/{id}/result: get: tags: - Submissions summary: Get submission result description: >- Returns the unified result envelope for a submission, including the extracted design system and stored artifacts. Results stream in: while the job runs you may receive a `200` with a partial `design_system`, and before the first checkpoint lands you receive `409 NOT_READY`. Keep polling until `status` is `completed` or `failed`. Use `sections` to narrow `result.design_system` to the sections you actually read. The full document is large, and `assets` and `layout` are commonly most of it. operationId: getSubmissionResult parameters: - $ref: '#/components/parameters/SubmissionId' - name: sections in: query required: false description: >- Comma-separated list of design-system sections to include, e.g. `?sections=colors,typography`. Omit for the full design system. Only `result.design_system` is filtered: the envelope and `result.artifacts` are always returned. An unknown section name returns `422`. style: form explode: false schema: type: array items: $ref: '#/components/schemas/SectionName' example: colors,typography responses: '200': description: The result envelope. May be partial while later steps complete. content: application/json: schema: $ref: '#/components/schemas/SubmissionResult' '404': $ref: '#/components/responses/NotFound' '409': description: The result is not ready yet. Keep polling. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: error: NOT_READY message: Result is not ready yet. '422': description: One of the requested section names is not a valid section. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: error: INVALID_REQUEST message: Unknown section name. '500': $ref: '#/components/responses/InternalError' security: - ApiKeyAuth: [] - {} components: parameters: SubmissionId: name: id in: path required: true description: The `submission_id` returned when the submission was created. schema: type: string schemas: SectionName: type: string description: A top-level section of `result.design_system`. enum: - profile - layout - colors - typography - surfaces - elevation - interactions - actions - navigation - data_display - structure - icons - assets - sections SubmissionResult: type: object description: Unified result envelope. May be partial while later steps complete. properties: submission_id: type: string extraction_id: type: - string - 'null' description: >- Identifier of the extraction this submission produced. `null` until one exists. status: type: string description: Submission status, e.g. `completed` or `failed`. source_url: type: string format: uri current_step: type: string step_started_at: type: - string - 'null' format: date-time updated_at: type: string format: date-time result_updated_at: type: string format: date-time cache_hit: type: boolean description: >- Whether the result was served from cache. When `true`, `completed_at` reflects the original extraction, not this request. accepted_at: type: string format: date-time completed_at: type: - string - 'null' format: date-time description: >- When the extraction completed: the freshness of the result. On a cache hit (`cache_hit` is `true`) this is the original extraction, not the current request, so it may predate this request. `null` while the submission is still running. result: type: object properties: design_system: type: object additionalProperties: true description: >- The extracted design system: a `profile` object (e.g. `profile.brand_name`), color palettes, typography, spacing, and component styles. See [The design system](/concepts/design-system) for the structure. artifacts: type: object properties: html: $ref: '#/components/schemas/Artifact' css: $ref: '#/components/schemas/Artifact' screenshot: $ref: '#/components/schemas/Artifact' description: Screenshot captured during the crawl. full_page_screenshot: $ref: '#/components/schemas/Artifact' description: Full-page screenshot of the rendered page. element_layout: $ref: '#/components/schemas/Artifact' description: Measured element geometry captured during the crawl. required: - submission_id - status - source_url Error: type: object description: >- Standard error envelope for non-2xx responses: the machine-readable `error` code and the human-readable `message` are nested under `detail`. Validation errors (`422`) and search failures (`502`, `503`) shape `detail` differently; see those responses. properties: detail: type: object properties: error: type: string description: Machine-readable error code. examples: - UNAUTHORIZED - FORBIDDEN - NOT_FOUND - NOT_READY message: type: string description: Human-readable explanation of the error. required: - error - message additionalProperties: true required: - detail Artifact: type: object description: A stored file produced during extraction. properties: path: type: string description: Storage path of the artifact. url: type: string format: uri description: URL to download the artifact. content_type: type: string description: MIME type, e.g. `text/html`. responses: NotFound: description: The resource was not found or is not accessible with these credentials. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: error: NOT_FOUND message: Submission not found InternalError: description: An unexpected server error occurred. The body is plain text. content: text/plain: example: Internal Server Error securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-API-Key description: >- API key issued by the Taste Engine. Create one in the dashboard at https://engine.tastelabs.com/app/api-keys. ````