canonical: https://jentic.com/apis/fera.ai/fera

# Fera API

The Fera API powers product reviews, photos, videos, ratings, and customer-generated content for online stores. It provides programmatic access to review moderation actions such as approve and decline, plus first-class endpoints for managing media uploads tied to specific products and orders. The 37-endpoint surface covers Customers, Media, Orders, Products, Ratings, Reviews, and Webhooks for end-to-end social-proof automation.

## For AI agents

Manage product reviews, photos, videos, and ratings for e-commerce stores via 37 REST endpoints, including moderation actions and webhook subscriptions.

## Scope

Does not handle payments, inventory, or order fulfilment - use for product reviews, ratings, and customer UGC only.

## Capabilities

- Create, approve, and decline product reviews tied to specific orders and customers
- Attach customer photos and videos to product listings as social proof
- Aggregate star ratings per product and retrieve them for storefront display
- Subscribe to webhooks for review submission, approval, and decline events
- List orders and customers to correlate reviews with verified purchases
- Moderate user-generated media before it appears on product detail pages

## Use cases

### Review Moderation Workflow

Automate moderation of user-generated reviews so an agent can approve clean submissions and decline ones containing prohibited content, instead of staff manually triaging the queue. Fera exposes dedicated PUT `/reviews/{id}/approve` and PUT `/reviews/{id}/decline` endpoints, removing the need for status-field updates on the base review object. Typical review volume is hundreds per day for a mid-sized store; agent moderation cuts response time from hours to seconds.

Example prompt: Fetch all reviews where state is pending, classify each via a content filter, and call PUT `/reviews/{id}/approve` or PUT `/reviews/{id}/decline` based on the result

### Verified-Purchase Review Requests

Trigger review request emails after orders ship by joining order data with customer records and generating review entries linked to the original purchase. The Fera API exposes orders, customers, and reviews as related resources so an agent can correlate them in a single workflow. Implementation through Fera typically takes a day; building an equivalent flow on a generic e-commerce stack takes a week.

Example prompt: List orders fulfilled in the last 7 days, fetch each customer record, and create a Fera review draft with order_id and customer_id pre-populated

### Visual Social Proof Galleries

Build dynamic photo and video galleries on product pages by pulling user-submitted media filtered by product. The /photos endpoints support listing, retrieving, and updating individual media items, and the API exposes both customer photos and review photos as separate resources. This replaces manual gallery curation with an agent-driven feed that surfaces fresh content as it is approved.

Example prompt: GET /photos filtered by product_id, return the 10 most recent approved photos, and update each to mark it as featured

### Agent-Driven Review Insights via Jentic

Through Jentic, an agent can answer questions like which products have low ratings or which customers leave the most reviews without writing custom integration code. Jentic stores Fera credentials in your Jentic One instance and exposes review, rating, and product operations as tools, so a Claude or GPT agent can call them directly. This unlocks ad-hoc analytics and customer-support workflows without engineering involvement.

Example prompt: Search Jentic for 'list product reviews', load the schema, and return the 5 products with the lowest average rating in the last 30 days

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/reviews` | List reviews |
| POST | `/reviews` | Create review |
| PUT | `/reviews/{id}/approve` | Approve review |
| PUT | `/reviews/{id}/decline` | Decline review |
| GET | `/photos` | List customer photos |
| POST | `/photos` | Upload customer photo |

## Key resources

- **Reviews** — Create, list, update, approve, and decline product reviews
- **Photos** — Manage customer-submitted product photos
- **Media** — Upload and attach video content to products and reviews
- **Ratings** — Retrieve aggregate star ratings per product
- **Customers** — Manage customer records linked to reviews and orders
- **Orders** — Reference orders to verify purchases tied to reviews
- **Webhooks** — Subscribe to review and media events

## Why Jentic

- **Setup:** Wiring the Fera API by hand means managing its X-API-Key header, tracking the v3 private endpoints, and handling pagination across reviews and photos yourself. Through Jentic you install once, import the Fera API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Fera puts the review id in the URL path (`/reviews/{id}/approve`, `/reviews/{id}/decline`), so a rule can pin your agent to acting on the reviews you allow. You choose the operations it may call, so a moderation action like decline is not included unless you add it alongside approve.
- **Credential handling:** Your Fera API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. The raw X-API-Key value never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'approve a customer review' or 'list product photos', and Jentic returns the matching Fera operation with its input schema, so the agent calls the right endpoint without browsing developers.fera.ai.

## Related APIs

- **Yotpo UGC API** — Larger UGC platform covering reviews, visual UGC, and loyalty in one suite
- **GoodReviews API** — Lightweight reviews collection alternative for smaller storefronts
- **Shopify Admin API** — Source of products, orders, and customers that Fera reviews reference

## FAQ

### What authentication does the Fera API use?

The Fera API uses an API key sent in the X-API-Key header. When called through Jentic the key is stored encrypted in your Jentic One instance and never appears in agent context.

### Can I approve reviews programmatically with the Fera API?

Yes. Fera exposes dedicated PUT `/reviews/{id}/approve` and PUT `/reviews/{id}/decline` endpoints, separate from the generic update review call, so moderation status changes are explicit and auditable.

### What are the rate limits for the Fera API?

Fera does not publish per-second limits in the OpenAPI spec; check the developer documentation at developers.fera.ai for the current quotas tied to your plan.

### How do I attach a photo to a product review through Jentic?

Search Jentic for 'attach product photo', load the POST /photos schema, and execute with product_id, customer_id, and the image URL. Run pip install jentic to get started.

### Does the Fera API support webhooks?

Yes. The Webhooks resource lets you subscribe to events such as review created, approved, and declined, so an agent can react to new content as it arrives instead of polling.

### Can the Fera API distinguish verified-purchase reviews?

Yes. Reviews can be linked to an order_id, which Fera uses to flag verified purchases. Agents can join /reviews and /orders to filter for verified entries.

### Can I limit what my agent is allowed to do with the Fera API?

Yes. Jentic One runs self-hosted, so your own rules decide which Fera operations and credentials the agent may use. Because Fera puts the review id in the URL path for actions like PUT `/reviews/{id}/approve` and PUT `/reviews/{id}/decline`, you can pin the agent to the reviews you allow and choose the exact operations it may call. For example, you can grant approve without ever exposing decline, and keep the API key injected only at execution time rather than in the agent's context.