Skip to main content
AI apps and agents use /search to find products across the web.

The request shape

Get an API key

Search requires an API key. Create a free account, then copy your key.
You get 1,000 free credits each month — that’s good for 1,000 searches. Extra usage is billed per call; see pricing for the breakdown.

Choose a search method

Search

Search with text and images.

Agentic search

Interpret longer shopping requests for an agent workflow.

Image search

Find visually similar products from an image URL or upload.
For a photo with several products in one scene, see Find products in an image.

Filters

Add optional filters to narrow your search.

Price

Constrain results to an offer price range.

Color

Find products that match a hex color palette.

Dimensions

Constrain length, width, height, or weight.

Brand

Filter by the company behind a product.

Website

Restrict results to retailer offers from selected websites.

Attributes

Filter on category-specific structured attributes.

Collections

Save a catalog scope and reuse it on search, browse, and conversations.

Start from an existing product

Look up a product URL

Get structured data from a URL, and offers at other retailers.

Find similar products

Get recommendations from a known Channel3 product ID.

Attribute clicks to your users

Send the x-user-id header on search (and other catalog) requests to tie buy-link clicks and commissions back to a user in your app.
Use a stable ID from your system (UUID, Clerk ID, etc.). Letters, numbers, and . _ @ -, up to 128 characters. Filter reporting by the same value — see By user.

Group a shopper conversation

Strongly recommended. Send x-conversation-id on every search in a shopper conversation. Channel3 uses it to group that session in your analytics, and a session is much easier to understand when every call shares the id.
Send the x-conversation-id header on each search in one shopper conversation. Channel3 stores that id with the search and groups every call that sends the same value.
Use a stable id from your app for that conversation. 1–64 characters: letters, numbers, underscores, and hyphens. Send the same header on later catalog requests in that conversation — browse, image search, similar products, and product detail — so they stay in the group.
Send x-conversation-id when your app calls /v1/search itself. The Conversational Agent is a separate path: pass conversation_id in the body of POST /v1/conversations to continue a thread, and Channel3 groups the searches that turn runs. See By conversation.

Next

Next: What you get. It explains how products, offers, prices, and buy links appear in a response.