Use the Recommendations API when you want to show related or connected items outside the main autocomplete flow.

What it does

These endpoints return products or documents that are related through structure, shared series, application fit, specs, user preference signals, or behavioral relationships such as co-click patterns.

They are a strong fit for:

  • related products modules
  • product detail page suggestions
  • accessory and compatibility flows
  • discovery rails and next-best-item experiences

Endpoints

  • GET /v1/graph/recommendations/structural
  • GET /v1/graph/recommendations/series
  • GET /v1/graph/recommendations/application
  • GET /v1/graph/recommendations/specs
  • POST /v1/graph/connected
  • GET /v1/graph/user-preferences
  • GET /v1/graph/co-clicked

How to think about these routes

  • structural is useful when your catalog has meaningful entity or hierarchy relationships
  • series is useful for model-family or product-line discovery
  • application helps when fit, use case, or compatibility matters
  • specs helps users discover similar items by technical attributes
  • connected is useful when you want a broader “related items” response shape
  • user-preferences and co-clicked help connect catalog relevance with observed behavior

When to use it

Use recommendations when you want to answer questions like:

  • what should this shopper see next?
  • what products are similar or compatible?
  • what do users often click together?