Review evidence
Ratings, methodology, product fit and the source-linked review corpus.
GET https://involvemereviews.com/api/v1/reviewsPublic evidence API
involve.me Reviews Developer API
Use a small, read-only JSON API to retrieve the review evidence and documented implementations published on this site. The OpenAPI 3.1 specification includes unique operation IDs, typed response schemas and structured errors for agent and function-calling clients.
Scope: this is the involve.me Reviews evidence API. It is not the involve.me product API and cannot access customer accounts, funnels, contacts, submissions or private data.
01
Quick start
No key, token or account is required.
Customer stories
Source-linked implementation records, outcomes and reported metrics.
GET https://involvemereviews.com/api/v1/customer-stories02
Machine-readable contract
Import the schema into an API client or agent tool registry.
OpenAPI 3.1
The specification is published at a predictable, canonical URL. Every operation has a unique operationId, a description, typed response bodies and documented error schemas. Both operations are anonymous and read-only.
03
Function calling
Register either OpenAPI operation as an anonymous, read-only tool.
listReviewEvidence
Use when an agent needs the published review corpus, rating snapshots, sentiment method or product-fit evidence. It takes no arguments and returns ReviewEvidenceResponse.
listCustomerStories
Use when an agent needs documented implementations, source URLs, use cases, outcomes or reported metrics. It takes no arguments and returns CustomerStoriesResponse.
Do not register these tools for product administration. Both endpoints are evidence retrieval only and have no authentication or write scope.
04
Errors and resolution
API errors are stable JSON rather than HTML pages.
{
"error": {
"code": "RESOURCE_NOT_FOUND",
"message": "No API resource exists at this path.",
"status": 404,
"resolution": "Use an endpoint listed in the OpenAPI specification.",
"docs_url": "https://involvemereviews.com/developers"
}
}Published responses may be cached for one hour. The API has no write operations, authentication flow or product-data permissions. The legacy reviews.json and customer-stories.json URLs remain available for compatibility.