---
title: "Reco API"
slug: "reco-api"
updated: 2024-12-12T14:42:45Z
published: 2024-12-12T14:42:45Z
canonical: "docs.mapp.com/reco-api"
---

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

# Reco API

The Reco API is a REST interface that allows recommendations from Marketing Automation to be retrieved and processed automatically by other systems, such as content management systems (CMS) or apps. This placement type provides a high level of flexibility for custom integrations.

While the Reco API offers advanced customization and performance benefits, the **on-site placement** (with its widget functionality) is an alternative option. The on-site placement provides built-in integration features, including styling and automatic tracking, for faster and easier implementation. Choosing between these placements depends on your specific requirements and available resources.

---

## Configuration for Reco API Placements

To configure and use the Reco API: ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/ss1(278).png)

1. Obtain the **Placement ID** and **API Endpoint URL** from the configuration screen under *Marketing Automation > Placements > Reco API*.
  - The **Placement ID** uniquely identifies the placement.
  - The **API Endpoint URL** is used to retrieve recommendations.
2. Identify the required **Input Keys** for each campaign using the placement.
  - These keys are specific to the recommendation logic configured for the campaigns.
  - Example:
    - **Cross-Selling Campaign**: Requires the Product ID as an input key.
    - **Last Seen Products Campaign**: Requires the User ID as an input key.

Find more information here: [Recommendation REST API - Get Started](/v1/docs/recommendation-rest-api-get-started).

---

## Things to Consider

When choosing between the Reco API and the **on-site placement** (with its widget functionality) for delivering recommendations, it’s important to evaluate the following aspects. These points highlight the key differences, opportunities, and challenges of using the Reco API compared to the on-site placement:

**Key Advantages of Reco API:**

- **High Performance**: Direct server-side integration ensures fast response times and optimized performance.
- **No Styling Effort**: Existing CMS templates can style recommendations directly, eliminating additional configuration efforts.
- **Reuse Existing Assortment Logic**: All assortment configurations from Marketing Automation remain available.
- **App Integration**: Recommendations can be implemented in apps, extending their use to mobile or other environments.

**Limitations Compared to On-Site Placement:**

- **Complex Implementation**: Requires development resources for integration and configuration.
- **No Automatic Tracking**: Tracking of interactions and performance must be implemented separately.
- **No Real-Time Target Groups**: Real-time behaviors cannot be used as target groups for this placement type.

## Related

- [Recommendation REST API - Get Started](/recommendation-rest-api-get-started.md)
- [Using the Recommendation API](/using-the-recommendation-api.md)