> ## 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 photography submission > Builds a photography profile from a brand's photos: the traits most of them share, what varies between them, and the tone measured from their pixels. Send 1 to 12 photos, each as an `https://` `url` or as `image_b64`. With one photo, the profile is that photo's own reading; with more, it keeps what most of them share. Graphics, renders, and composites are read and then left out of the profile. The job runs asynchronously: poll [`GET /design/submissions/{id}`](/api-reference/endpoint/get-submission) until the status is `completed` or `failed`, then read the profile from [`GET /design/submissions/{id}/result`](/api-reference/endpoint/get-submission-result). A failed submission's `error` starts with `NOT_ENOUGH_PHOTOS` (none of the photos is a usable photograph: send others) or `PHOTO_READS_FAILED` (retry the same request). Costs 2 credits, refunded when no profile comes back. See [Photography profile](/concepts/photography-profile). ## OpenAPI ````yaml api-reference/openapi.json POST /design/submissions/photography 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/photography: post: tags: - Submissions summary: Create photography submission description: >- Builds a photography profile from a brand's photos: the traits most of them share, what varies between them, and the tone measured from their pixels. Send 1 to 12 photos, each as an `https://` `url` or as `image_b64`. With one photo, the profile is that photo's own reading; with more, it keeps what most of them share. Graphics, renders, and composites are read and then left out of the profile. The job runs asynchronously: poll [`GET /design/submissions/{id}`](/api-reference/endpoint/get-submission) until the status is `completed` or `failed`, then read the profile from [`GET /design/submissions/{id}/result`](/api-reference/endpoint/get-submission-result). A failed submission's `error` starts with `NOT_ENOUGH_PHOTOS` (none of the photos is a usable photograph: send others) or `PHOTO_READS_FAILED` (retry the same request). Costs 2 credits, refunded when no profile comes back. See [Photography profile](/concepts/photography-profile). operationId: createPhotographySubmission requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/PhotographySubmissionCreate' examples: urls: summary: Photos by URL value: photos: - url: https://images.example.com/campaign-1.jpg - url: https://images.example.com/campaign-2.jpg upload: summary: An uploaded photo value: photos: - image_b64: /9j/4AAQSkZJRgABAQ... responses: '202': description: The photos were accepted and queued for reading. content: application/json: schema: $ref: '#/components/schemas/SubmissionAccepted' example: submission_id: 5fb12de2-b640-4333-954a-a41703406b9a status: accepted source_url: https://images.example.com/campaign-1.jpg accepted_at: '2026-10-27T12:34:43Z' '401': $ref: '#/components/responses/Unauthorized' '402': description: Not enough credits (`INSUFFICIENT_CREDITS`). content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: error: INSUFFICIENT_CREDITS message: Not enough credits for this request. balance: 0 required: 2 '403': $ref: '#/components/responses/Forbidden' '422': description: >- The request failed validation: no photos or more than 12, a photo with both or neither of `url` and `image_b64`, a URL that is not public `https://`, or an upload that is not a PNG, JPEG, or WebP image. `detail` lists the issues. content: application/json: example: detail: - type: value_error loc: - body - photos - 0 - url msg: Value error, URL must be a valid https:// URL with a host input: http://images.example.com/campaign-1.jpg '500': $ref: '#/components/responses/InternalError' components: schemas: PhotographySubmissionCreate: type: object required: - photos additionalProperties: false properties: photos: type: array minItems: 1 maxItems: 12 items: $ref: '#/components/schemas/PhotoInput' description: >- The brand's photos. From a brand kit, send the `do` and `example` assets of `photography.examples`. 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 PhotoInput: type: object description: 'One photo: exactly one of `url` or `image_b64`.' properties: url: type: string format: uri maxLength: 4096 description: >- Public `https://` URL of the photo. It is downloaded when the photo is read. image_b64: type: string description: 'The photo as base64: PNG, JPEG, or WebP, up to 64 megapixels.' oneOf: - required: - url - required: - image_b64 additionalProperties: false 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.