canonical: https://jentic.com/apis/reviewrover.co/reviewrover

# Review Rover API

Review Rover API for review management and customer feedback. The API exposes 19 endpoints secured with bearer authentication.

## For AI agents

Programmatically create contact, list contacts. Covers 19 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for social media only.

## Capabilities

- Create contact
- List contacts
- Get contact
- Update contact
- Delete contact

## Use cases

### Social Media Operations

Use the Review Rover API to perform social media operations programmatically. The API provides 19 endpoints covering core functionality including create contact, list contacts, get contact.

Example prompt: Call POST /contacts to create contact

### Automated Campaigns Management

Automate campaigns operations by combining multiple Review Rover API endpoints. Agents can list contacts and then get contact in a single workflow.

Example prompt: Call GET /contacts to list contacts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Review Rover API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'create contact', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/contacts` | Create contact |
| GET | `/contacts` | List contacts |
| GET | `/contacts/{id}` | Get contact |
| PUT | `/contacts/{id}` | Update contact |
| DELETE | `/contacts/{id}` | Delete contact |
| POST | `/campaigns` | Create campaign |
| GET | `/campaigns` | List campaigns |
| POST | `/enrollments` | Create enrollment |

## Key resources

- **Campaigns** — Operations related to Campaigns
- **Communications** — Operations related to Communications
- **Contacts** — Operations related to Contacts
- **Enrollments** — Operations related to Enrollments
- **Feedbacks** — Operations related to Feedbacks

## Why Jentic

- **Setup:** Wiring the Review Rover API by hand means handling its bearer token auth, attaching that token to every call to api.reviewrover.co, and managing retries yourself. Through Jentic you install once, import the Review Rover API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Review Rover puts the contact id in the URL path (`/contacts/{id}`), so a rule can pin your agent to one contact: it can read that contact and nothing else. You choose the operations it may call, so destructive ones like deleting a contact or creating campaigns are not included unless you add them.
- **Credential handling:** Your Review Rover token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a contact' or 'enroll a contact in a campaign', and Jentic returns the matching Review Rover API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook** — Alternative social media API
- **Twitter** — Alternative social media API
- **Linkedin** — Complementary social media API

## FAQ

### What authentication does the Review Rover API use?

The Review Rover API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create contact with the Review Rover API?

Yes. Use the POST /contacts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Review Rover API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create contact through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create contact'. Jentic returns the matching Review Rover API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Review Rover API have?

The Review Rover API exposes 19 endpoints covering campaigns, communications, contacts operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Review Rover operations and credentials the agent may use. Since the contact id sits in the URL path (`/contacts/{id}`), a rule can pin the agent to a single contact so it reads only that record and nothing else. You also choose the operations it may call, so destructive ones like deleting a contact or creating campaigns are excluded unless you explicitly add them.