canonical: https://jentic.com/apis/reviewharvest.com/reviewharvest

# Review Harvest API

Review Harvest is a review management platform. The API supports creating integrations, managing contacts, and validating connections. The API exposes 4 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a new integration, delete an integration. Covers 4 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Create a new integration
- Delete an integration
- Validate API connection
- Add a contact
- Monitor Review Harvest API operational status and events

## Use cases

### CRM Operations

Use the Review Harvest API to perform crm operations programmatically. The API provides 4 endpoints covering core functionality including create a new integration, delete an integration, validate API connection.

Example prompt: Call POST /create to create a new integration

### Automated Authentication Management

Automate authentication operations by combining multiple Review Harvest API endpoints. Agents can delete an integration and then validate API connection in a single workflow.

Example prompt: Call GET `/delete/{id}` to delete an integration, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Review Harvest 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 apiKey tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/create` | Create a new integration |
| GET | `/delete/{id}` | Delete an integration |
| POST | `/connection` | Validate API connection |
| POST | `/add` | Add a contact |

## Key resources

- **Authentication** — Operations related to Authentication
- **Contacts** — Operations related to Contacts
- **Integrations** — Operations related to Integrations

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 48 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/reviewharvest.com/reviewharvest/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Review Harvest API by hand means appending its api_key query parameter to every request, pointing calls at the integration host on integrations.reviewharvest.com, and handling retries yourself. Through Jentic you install once, import the Review Harvest API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Review Harvest's integration targets travel in the request body and query rather than as a resource you can pin, so limit the agent to the operations it needs, such as creating a connection or adding an integration. You choose that set, so operations like deleting an integration are not included unless you add them.
- **Credential handling:** Your Review Harvest API key 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 new integration' or 'test a connection', and Jentic returns the matching Review Harvest API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

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

The Review Harvest API uses an API key passed in the `api_key` query. 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 a new integration with the Review Harvest API?

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

### What are the rate limits for the Review Harvest 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 a new integration through Jentic?

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

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

The Review Harvest API exposes 4 endpoints covering authentication, contacts, integrations operations.

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

Yes. Because Review Harvest's integration targets travel in the request body and query rather than as a resource you can pin, you scope the agent by choosing exactly which operations it may call in your self-hosted Jentic One instance, where your own rules decide the permitted operations and credentials. You might allow it to validate a connection with POST /connection, create an integration with POST /create, and add a contact with POST /add, while withholding the destructive GET `/delete/{id}` that removes an integration. Only the operations you grant are available to the agent, and the API key stays encrypted and injected at execution time so it never enters the agent's context.