Yotpo

Yotpo is an eCommerce marketing platform for reviews, ratings, SMS and email marketing, loyalty, and subscriptions. The Yotpo Core API exposes reviews, questions and answers, product bottomlines, email analytics, webhooks, and store data, and lets you push customers, orders, products, and behavioral events back into your Yotpo store.

Power end-to-end data operations for your Yotpo API with Nexla. Our bi-directional Yotpo connector is purpose-built for Yotpo, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Yotpo or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Yotpo workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Yotpo credential in Nexla, you need your Yotpo Store ID and an API access token. Yotpo authenticates most Core API requests with a bearer access token that you generate from your Store ID and API secret key.

To obtain your Yotpo credentials, follow these steps:

1. Sign in to your Yotpo account as an account administrator. The API secret key is only visible to administrators.

2. Locate your Store ID (previously called the "app key") and your API secret key in your Yotpo account settings, under the store or API settings for your account.

3. Generate an access token by calling the Yotpo authentication endpoint with your Store ID and API secret key. Yotpo returns a token that authenticates subsequent Core API requests.

4. Store the generated access token and your Store ID securely, as you will provide both when configuring your Nexla credential. If the token expires and requests begin returning a 401 error, generate a new token and update your credential.

In Nexla, the access token is sent in the request's Authorization header as a bearer token, and the Store ID identifies your store for store-scoped endpoints. For details about authentication, generating tokens, and available resources, see the Yotpo Core API Reference.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	API key.
Store ID	Yes	No	Your Yotpo store ID.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Yotpo access token in the API Key field. This value is sent in the Authorization header as a bearer token to authenticate all Yotpo API requests and must be kept confidential.

4. Enter your Yotpo store ID in the Store ID field. This identifies your store for store-scoped Yotpo endpoints.

   If your access token is compromised, generate a new token from your Yotpo account and update this credential. Access tokens can expire; if requests begin returning a 401 error, generate a new token.

   For detailed information about Yotpo authentication and available endpoints, see the Yotpo Core API Reference.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Yotpo connector tile, then select the credential that will be used to connect to the Yotpo instance, and click Next; or, create a new Yotpo credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Yotpo endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Reviews

Retrieve reviews. Use this template to ingest reviews submitted for your store for analysis, reporting, or moderation workflows.

• This endpoint returns reviews for your Yotpo store. Nexla handles pagination automatically to fetch all available records.

[Rest API] List Questions

Retrieve all Q&A questions submitted for the store. Use this template to ingest customer questions for analysis or to feed downstream systems.

• This endpoint returns Q&A questions for your Yotpo store. Nexla handles pagination automatically to fetch all available records.

[Rest API] List Products Bottomline

Retrieve aggregate review counts and average scores for all products in the store. Use this template to ingest per-product rating summaries.

• This endpoint returns aggregate review counts and average scores across the products in your store. Nexla handles pagination automatically to fetch all available records.

[Rest API] List Email Analytics

Retrieve email_analytics. Use this template to ingest email campaign analytics from your Yotpo store.

• This endpoint returns email analytics data for your Yotpo store. Nexla handles pagination automatically to fetch all available records.

[Rest API] List Raw Data

Retrieve raw_data. Use this template to ingest raw event or record data exposed by your Yotpo store.

• This endpoint returns raw data for your Yotpo store. Nexla handles pagination automatically to fetch all available records.

[Rest API] List Unsubscribers

Retrieve unsubscribers. Use this template to ingest the list of email addresses that have opted out of your Yotpo communications.

• This endpoint returns unsubscribers for your Yotpo store. Nexla handles pagination automatically to fetch all available records.

[Rest API] List Webhooks

Retrieve webhooks. Use this template to ingest the webhooks configured for your Yotpo store.

• This endpoint returns the webhooks registered for your Yotpo store. Nexla handles pagination automatically to fetch all available records.

[Rest API] List Webhook Events

Retrieve webhook_events. Use this template to ingest the events delivered to your Yotpo store's webhooks.

• This endpoint returns webhook events for your Yotpo store. Nexla handles pagination automatically to fetch all available records.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Yotpo data sources can also be manually configured to ingest data from any valid Yotpo API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Yotpo data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Yotpo destination, and select the Send to Destination option from the menu. Select the Yotpo connector from the list of available destination connectors, then select the credential that will be used to connect to the Yotpo store, and click Next; or, create a new Yotpo credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Yotpo endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create or Update Customer

Create or update a customer record in your Yotpo store. Each record from your Nexset is sent as a separate request to create or update the corresponding customer.

• This endpoint sends data as JSON in the request body. Ensure each record includes the fields required by the Yotpo customer API.

[Rest API] Create Order

Register a new store transaction (order) in Yotpo. Each record from your Nexset is sent as a separate request to create an order.

• This endpoint sends data as JSON in the request body. Ensure each record includes the fields required by the Yotpo order API.

[Rest API] Update Order

Update fulfillment and other details for an existing order in Yotpo. Each record from your Nexset is sent as a separate request to update the corresponding order.

• This endpoint sends data as JSON in the request body. Include the identifier of the order to be updated along with the fields to change.

[Rest API] Create Product

Add a new product to the Yotpo product catalog. Each record from your Nexset is sent as a separate request to create a product.

• This endpoint sends data as JSON in the request body. Ensure each record includes the fields required by the Yotpo product API.

[Rest API] Create Customer Event

Enrich customer records with custom behavioral events in Yotpo. Each record from your Nexset is sent as a separate request to record a customer event.

• This endpoint sends data as JSON in the request body. Ensure each record includes the fields required by the Yotpo customer event API.

[Rest API] Create Question

Submit a new Q&A question to the store's Q&A widget, optionally sending a confirmation email. Each record from your Nexset is sent as a separate request.

• This endpoint sends data as JSON in the request body. Ensure each record includes the fields required by the Yotpo Q&A API.

[Rest API] Create Answer

Submit an answer to a question in the store's Q&A widget. Each record from your Nexset is sent as a separate request.

• This endpoint sends data as JSON in the request body. Include the identifier of the question being answered along with the answer content.

[Rest API] Unsubscribe Email

Opt an email address out of future Yotpo review request communications. Each record from your Nexset is sent as a separate request.

• This endpoint sends data as JSON in the request body. Ensure each record includes the email address to opt out.

Manual configuration

Yotpo destinations can also be manually configured to send data to any valid Yotpo API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Yotpo APIs typically expect JSON format for most operations. For update operations, include the identifier of the object to be updated as required by the endpoint.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Yotpo endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Yotpo endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.