> ## 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. # Create brand kit submission > Extracts a brand kit from a brand guidelines PDF: profile and voice, colors with their proportions, typography, logo variants and misuse, photography, graphics, applications, layout, buttons, cards, motion, and the book's rules. The job runs asynchronously: poll `GET /design/submissions/{id}/result` until the status is `completed` or `failed`. The result's `design_system` has `kind: "brand_kit"` and the [BrandKitDesignSystem](/concepts/brand-kit#read-the-result) shape. Every upload is a fresh extraction and is never served from cache. The PDF can be up to 50 MB; the extractor reads up to the first 150 pages. See [Brand kit](/concepts/brand-kit). ## OpenAPI ````yaml api-reference/openapi.json POST /design/submissions/brand-kit 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/brand-kit: post: tags: - Submissions summary: Create brand kit submission description: >- Extracts a brand kit from a brand guidelines PDF: profile and voice, colors with their proportions, typography, logo variants and misuse, photography, graphics, applications, layout, buttons, cards, motion, and the book's rules. The job runs asynchronously: poll `GET /design/submissions/{id}/result` until the status is `completed` or `failed`. The result's `design_system` has `kind: "brand_kit"` and the [BrandKitDesignSystem](/concepts/brand-kit#read-the-result) shape. Every upload is a fresh extraction and is never served from cache. The PDF can be up to 50 MB; the extractor reads up to the first 150 pages. See [Brand kit](/concepts/brand-kit). operationId: createBrandKitSubmission requestBody: required: true content: multipart/form-data: schema: type: object required: - file properties: file: type: string format: binary description: >- Brand guidelines PDF (brand book, brand toolkit, identity deck). responses: '202': description: The brand kit was accepted and queued for processing. content: application/json: schema: $ref: '#/components/schemas/SubmissionAccepted' example: submission_id: 6f1c2a9e-0b7d-4e55-9a3c-1d2e3f4a5b6c status: accepted source_url: file://brand-guidelines.pdf accepted_at: '2026-10-16T12:00:00Z' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '413': description: The PDF is larger than 50 MB. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: error: FILE_TOO_LARGE message: file exceeds 50000000 bytes '422': description: >- The file is not a PDF (`INVALID_FILE_TYPE`) or is empty (`EMPTY_FILE`). content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: error: INVALID_FILE_TYPE message: file must be a PDF (.pdf) '500': $ref: '#/components/responses/InternalError' components: schemas: SubmissionAccepted: type: object properties: submission_id: type: string status: type: string enum: - accepted source_url: type: string format: uri accepted_at: type: string format: date-time required: - submission_id - status - source_url - accepted_at 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 responses: Unauthorized: description: The API key is missing, invalid, or expired. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: error: UNAUTHORIZED message: Bearer token or X-API-Key required Forbidden: description: The API key is valid but is not allowed to call this endpoint. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: error: FORBIDDEN message: This key is not allowed to call this endpoint. 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. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.