Legacy Search API

Name: Legacy Search API API
Brand: Legacy Search API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontapiKey15 EndpointsREST

For Agents

Programmatically get product search of who saw also saw (deprecated), get product search of who saw also bought (deprecated). Covers 15 operations with apiKey authentication.

Connect the Legacy Search API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Legacy Search API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Legacy Search API API.

Get product search of who saw also saw (deprecated)

Manage e commerce data programmatically

Integrate Legacy Search API into automated workflows

Query and filter Legacy Search API records by parameters

GET STARTED

Start building with Legacy Search API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Legacy Search API, keeping it validated and agent-ready.

> Check the new [Search onboarding guide](https://developers.vtex.com/docs/guides/search-overview). We created this guide to improve the onboarding experience for developers at VTEX. It assembles all documentation on our Developer Portal about Search and is organized by focusing on the developer's journey. This API lets you search and sort products in the Catalog using Fulltext, Category and Brand. The API exposes 15 endpoints secured with apiKey authentication.

Use Cases

Patterns agents use Legacy Search API API for, with concrete tasks.

★ E-Commerce Operations

Use the Legacy Search API to perform e commerce operations programmatically. The API provides 15 endpoints covering core functionality including get product search of who saw also saw (deprecated), get product search of who saw also bought (deprecated), get product search of who bought also bought (deprecated).

Call GET /api/catalog_system/pub/products/crossselling/whosawalsosaw/{productId} to get product search of who saw also saw (deprecated)

Automated CrossSelling Management

Automate crossselling operations by combining multiple Legacy Search API endpoints. Agents can get product search of who saw also bought (deprecated) and then get product search of who bought also bought (deprecated) in a single workflow.

Call GET /api/catalog_system/pub/products/crossselling/whosawalsobought/{productId} to get product search of who saw also bought (deprecated), then verify the result

AI Agent Integration via Jentic

AI agents discover and call Legacy Search API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'get product search of who saw also saw (deprecated)', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

15 endpoints — > check the new [search onboarding guide](https://developers.

METHOD

PATH

DESCRIPTION

GET

/api/catalog_system/pub/products/crossselling/whosawalsosaw/{productId}

Get product search of who saw also saw (deprecated)

GET

/api/catalog_system/pub/products/crossselling/whosawalsobought/{productId}

Get product search of who saw also bought (deprecated)

GET

/api/catalog_system/pub/products/crossselling/whoboughtalsobought/{productId}

Get product search of who bought also bought (deprecated)

GET

/api/catalog_system/pub/products/crossselling/showtogether/{productId}

Get product search of show together

GET

/api/catalog_system/pub/products/crossselling/accessories/{productId}

Get product search of accessories

GET

/api/catalog_system/pub/products/crossselling/similars/{productId}

Get product search of similars

GET

/api/catalog_system/pub/products/crossselling/suggestions/{productId}

Get product search of suggestions

GET

/api/catalog_system/pub/products/search/{search}

Search for products

GET

/api/catalog_system/pub/products/crossselling/whosawalsosaw/{productId}

Get product search of who saw also saw (deprecated)

GET

/api/catalog_system/pub/products/crossselling/whosawalsobought/{productId}

Get product search of who saw also bought (deprecated)

GET

/api/catalog_system/pub/products/crossselling/whoboughtalsobought/{productId}

Get product search of who bought also bought (deprecated)

GET

/api/catalog_system/pub/products/crossselling/showtogether/{productId}

Get product search of show together

GET

/api/catalog_system/pub/products/crossselling/accessories/{productId}

Get product search of accessories

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Legacy Search API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get product search of who saw also saw (deprecated)') and Jentic returns the matching Legacy Search API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Legacy Search API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using Legacy Search API API through Jentic.

What authentication does the Legacy Search API use?

The Legacy Search API uses an API key passed in the `X-VTEX-API-AppKey` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I get product search of who saw also saw (deprecated) with the Legacy Search API?

Yes. Use the GET /api/catalog_system/pub/products/crossselling/whosawalsosaw/{productId} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Legacy Search API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get product search of who saw also saw (deprecated) through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get product search of who saw also saw (deprecated)'. Jentic returns the matching Legacy Search API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Legacy Search API have?

The Legacy Search API exposes 15 endpoints covering crossselling, search, offers operations.