Overview

Instead of using Perselio's built-in Widgets, you can call the Recommendation API directly and render product recommendations in your own front-end. This approach gives you full control over layout and presentation while still leveraging Perselio's personalization and AI-ranked results.

When to Use API Integration

API integration is a good fit when:

• You want to render recommendations inside your own UI components with custom styling and layout.
• You do not need Perselio to manage widget rendering, design tokens, or front-end assets.
• Your item feed does not need to carry widget-specific display fields (labels, coupons, images, etc.) — you can source that data from your own systems at render time.

Advantages

• No widget dependency — you are not tied to Perselio's widget framework, carousel layouts, or styling constraints. Render recommendations however you want.
• Leaner item feed — fields that exist only for widget display (e.g., label colors, coupon badges, alternative images) can be omitted from the feed, keeping it smaller and simpler to maintain.

Things to Consider

• API integration required — your development team needs to implement HTTP calls to the Recommendation API, handle responses, and render results. See the API reference for request/response details.
• User identification is essential — every API call must include zid (zone ID) and uid (user ID) so that Perselio can return personalized results. These identifiers connect API requests to the behavioral data collected by the Data Collector.
• Scenarios must be configured and trained — recommendation scenarios (the models that power each recommendation surface) need to be defined and trained before the API can return results. Work with the Perselio team to set up the scenarios you need.