2 APIs across 2 product groups.
| I want to... | Use | Why |
|---|---|---|
| Read, create, search, or vote on product reviews and ratings | Yotpo UGC API | The UGC API owns reviews, Q&A, product bottom-line ratings, and voting. |
| Read orders, products, customers, and update fulfillments | Yotpo App Developer API | The App Developer API exposes storefront records like orders, products, and fulfillments. |
| Look up product review content | Yotpo UGC API | Product reviews and ratings live in the UGC API, not the storefront API. |
| Look up product records and variants | Yotpo App Developer API | Product listings, variants, and promoted products come from the App Developer API. |
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Yotpo APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fyotpo.com" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fyotpo.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
Once connected, ask your agent something like: “read Yotpo product reviews and connect them to orders and products”.
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Yotpo by hand means running the UGC API's OAuth token exchange, minting an App Developer API key for the X-Yotpo-Token header, and handling retries on each call yourself. With Jentic One installed you add either Yotpo API from the Jentic directory to your workspace and your agent calls it.
Permission scoping
Yotpo puts review, product, and fulfillment ids in the URL path, so your own rules can pin an agent to specific records and specific operations. Reads like fetching a product's reviews can be allowed while writes such as creating a review or updating a fulfillment stay out unless you add them.
Credential isolation
Each Yotpo credential, the UGC bearer token and the App Developer API key, is stored encrypted by your own Jentic One instance and injected at execution time, so raw secrets never enter the agent's prompt, logs, or context.
Specific to using Yotpo APIs through Jentic.
What can an agent do across Yotpo's APIs?
An agent can read and create product reviews, fetch ratings, search review content, and vote on reviews through the UGC API, and read orders, products, customers, variants, and fulfillments and update fulfillment status through the App Developer API. The shared link between them is the product, so review data can be joined to order and product records.
Do the two Yotpo APIs share one credential?
No. The Yotpo UGC API authenticates with a bearer token obtained from its OAuth token exchange, and the Yotpo App Developer API authenticates with an API key in the X-Yotpo-Token header. An agent that spans both needs both credentials configured.
Which Yotpo API should I use for reviews versus orders?
Use the UGC API for reviews, ratings, Q&A, coupons, and email analytics. Use the App Developer API for orders, products, customers, variants, and fulfillments. Product identifiers appear in both, which lets you connect a review to the product and order it belongs to.
Can I combine both Yotpo APIs in one workflow?
Yes. A common pattern is to pull orders and products from the App Developer API and then fetch the matching reviews and ratings from the UGC API, or to check a product rating before updating a fulfillment. Product ids returned by one API are used to query the other.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
For Agents
An agent can read and create product reviews, fetch product ratings, search review content, and vote on reviews through the UGC API, then pull the related orders, products, customers, and fulfillments and update fulfillment status through the App Developer API.
Yotpo pairs a user-generated-content API for reviews, Q&A, coupons, and email analytics with a storefront API for orders, products, and fulfillments, so review and rating data can be tied back to the commerce records it describes. This makes it distinct from analytics-only or store-only APIs that cover just one side of that relationship.
Use for: Reading and creating product reviews, ratings, Q&A, and coupons, and reading orders, products, customers, and fulfillments for a Yotpo commerce account
Not supported: payment processing, email sending, crm records, real-time streaming, on-prem deployment
Credentials: No single credential covers both: the Yotpo UGC API uses a bearer token from its OAuth token exchange, while the Yotpo App Developer API uses an API key sent in the X-Yotpo-Token header.
All 2 Yotpo OpenAPI specs are vendor-official and indexed by Jentic, kept validated and agent-ready.
Yotpo is a commerce marketing platform whose APIs cover user-generated content and storefront data. The Yotpo UGC API handles reviews, Q&A, coupons, visual content, and email analytics, while the Yotpo App Developer API handles orders, products, customers, and fulfillments. Together they let programs read shopper reviews and ratings and connect them to the underlying order and product records.
Each workflow spans multiple Yotpo APIs. Jentic routes each operation to the right API automatically.
Attach reviews to their orders
Pull a customer's orders from the App Developer API, then fetch the reviews and ratings for the products in those orders from the UGC API to see what buyers said about what they bought.
Call GET /orders to retrieve a customer's orders, then for each product call GET /products/{product_id}/reviews to gather its reviews
Yotpo App Developer API + Yotpo UGC API
Rating check before fulfillment update
Read a product's rating from the UGC API and its record from the App Developer API before updating a fulfillment, so low-rated items can be flagged in the same workflow.
Call GET /products/{product_id}/bottomline for the rating and GET /products/{product_id} for the record, then PATCH /orders/fulfillments/{id} to update fulfillment
Yotpo UGC API + Yotpo App Developer API
Review coverage report by product
List products and variants from the App Developer API and cross-reference each against its reviews in the UGC API to report which products lack reviews.
Call GET /products to list products, then GET /products/{product_id}/reviews for each to find products with no reviews
Yotpo App Developer API + Yotpo UGC API
Intent-based discovery
An agent searches the Jentic directory by intent, such as getting a product's reviews or listing orders, and Jentic returns the matching Yotpo operation and its input schema so the agent calls the right endpoint across both APIs without browsing the reference docs.
What is out of scope for Yotpo's APIs?
These APIs do not process payments, send email, or store crm records. They focus on user-generated content and storefront data such as reviews, ratings, orders, products, and fulfillments for a Yotpo commerce account.
How does an agent find the right Yotpo operation?
The agent searches Jentic by intent, such as getting a product's reviews or listing orders, and Jentic returns the matching Yotpo operation with its input schema. This avoids reading the reference docs to locate an endpoint by hand.
All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.