> ## Documentation Index
> Fetch the complete documentation index at: https://docs.preezie.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API reference

> Use product discovery operations and retrieve generated product content.

The preezie API provides product discovery operations and generated content for product detail pages.

## Core Intent API

The Core Intent API exposes four dedicated product-discovery operations:

* **Search** finds products that match a natural-language request.
* **Similar-to** discovers products similar to a base product.
* **Compare** compares products selected by the shopper.
* **Bundle** suggests complementary products.

Each operation uses the same request structure. The route selects the intent, so you do not send an `intent` field.

## Streaming responses

Successful responses use server-sent events with the `text/event-stream` content type. Each event contains a JSON value:

```text theme={null}
data: {"chatStream":"I found several matching products."}

data: {"data":{"responseType":"ProductSearch","responsePayload":[{"id":"product-123"}]}}

```

Set `operationHideAiMessage` to `true` to omit `chatStream` events. By default, product results in `responsePayload` contain only their `id`; set `operationReturnFullProductInfo` to `true` when the complete product data is required.

The source contract is maintained in `openapi/preezie-api.json`.

## Product content

The Product Content API returns pre-generated content for a product detail page:

* **FAQs** returns shopper-focused questions and answers.
* **Highlights** returns concise product selling points.

These endpoints return JSON and require a product ID in the URL plus the `Tenantid` request header. They do not use the Core Intent request body or SSE response format.