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

# Revnu API

The Revnu API controls Revnu's go-to-market agent for software businesses, routing anything that sends, publishes, or spends through the same approval queue the dashboard uses. It lists review cards waiting for approval and lets you answer, send, snooze, dismiss, or request changes on each, and it composes, runs, pauses, and resumes recurring workflows from a plain-words schedule. Leads come back with status, score, contacts, and research, alongside a do-not-contact block list, a per-channel results scoreboard, and a chat channel to message the agent directly. Separate endpoints serve published blog posts to a Content API token and accept server-side signup, booking, and payment events for attribution.

## For AI agents

Approve or dismiss Revnu's pending outreach and content cards, run and pause recurring GTM workflows, read leads and results, and maintain the do-not-contact block list.

## Scope

Does not host a CRM, process customer payments, or send email outside its approval queue. Use for controlling Revnu's GTM agent, its workflows, leads, and content only.

## Capabilities

- Review Revnu's approval queue and answer, send, snooze, dismiss, or request changes on each card
- Compose recurring workflows from a plain-words schedule and run, pause, resume, or delete them
- Page through leads by status or workflowRunId and read one lead's contacts, draft, and research
- Block companies, mailboxes, or LinkedIn profiles from outreach, up to 500 per call
- Read the per-channel growth scoreboard covering email, ads, SEO, social, and LinkedIn
- Message the Revnu agent and poll its reply by requestId
- Serve published blog posts with markdown, HTML, and JSON-LD to your own site through the Content API

## Use cases

### Approving GTM work from your own agent

Revnu holds outbound email, posts, and spend in a review queue until someone approves them. A developer's coding or ops agent can work that queue through Jentic: it searches by intent, gets the reviewList and reviewAnswer operations with their input schemas, and calls them with the personal token injected at execution time. Leaving reviewSend out of the allowed operations keeps the agent from sending real email while it triages.

Example prompt: Call GET `/api/v1/review` with status pending, read each card with GET `/api/v1/review/{id}`, and call POST `/api/v1/review/{id}/snooze` on any card that needs the founder's input

### Scheduling and controlling recurring workflows

Recurring GTM jobs such as a weekly prospect list or a monthly SEO refresh live as Revnu workflows. POST `/api/v1/workflows` composes one from a schedule in plain words and a list of steps, POST `/api/v1/workflows/{id}/runs` starts the next run now without changing the schedule, and the pause and resume operations stop and restart it without losing history. GET `/api/v1/workflows/{id}/runs` returns per-step outcomes for each run.

Example prompt: List workflows via GET `/api/v1/workflows`, find the one named 'Weekly prospect list', start a run via POST `/api/v1/workflows/{id}/runs`, then read GET `/api/v1/workflows/{id}/runs` for the queued run's status

### Keeping outreach off the wrong contacts

Before Revnu researches or emails anyone, its send and research gates check the block list. POST `/api/v1/blocklist` adds domains, email addresses, or LinkedIn profiles, up to 500 per call, and is idempotent, so re-sending a whole list is safe. GET `/api/v1/blocklist` pages through the entries and DELETE `/api/v1/blocklist/{id}` removes one, except for addresses that unsubscribed, which stay blocked.

Example prompt: Add the customer domains from the CRM export to the block list via POST `/api/v1/blocklist`, then confirm the added and existing counts in the response

### Attributing signups and payments

Revnu ties results back to the channel a visitor came from when your server reports the outcome. POST `/api/measurement/events`, authenticated with a server-side event key, records signups, booked calls, and payments, and the response says whether the event matched a visitor and counted toward the site's win definition. GET `/api/v1/results` then shows the per-channel scoreboard.

Example prompt: Send a signup event to POST `/api/measurement/events` from the server after a new account is created, then read GET `/api/v1/results` to see the email and SEO sections

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/review` | List the review queue |
| POST | `/api/v1/review/{id}/answer` | Answer a review card |
| POST | `/api/v1/workflows` | Create a recurring workflow |
| POST | `/api/v1/workflows/{id}/runs` | Run a workflow now |
| GET | `/api/v1/leads` | List leads |
| POST | `/api/v1/blocklist` | Add block list entries |
| GET | `/api/v1/results` | Get the results scoreboard |
| GET | `/api/content/v1/posts` | List published posts |

## Key resources

- **Review cards** — Pending approvals with answer, send, request-changes, snooze, and dismiss actions
- **Workflows** — Recurring workflows with schedule, steps, run history, and run-now, pause, resume, and delete controls
- **Leads and block list** — Leads with status, score, contacts, draft, and research, plus do-not-contact entries by domain, email, or LinkedIn profile
- **Agent and results** — Message the Revnu agent, read its thread and status, and read the per-channel results scoreboard
- **Content API** — Published blog posts with render-ready markdown, HTML, head metadata, and JSON-LD
- **Event API and setup** — Server-side conversion events, plus onboarding steps for website, confirmation, checkout link, and start

## 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:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 68 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 73 / 100
- **View full report:** https://jentic.com/apis/revnu.com/revnu/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 Revnu by hand means juggling three bearer tokens, a scoped personal token for the main API, a Content API token, and a server-side event key, and routing each call to the right one. Through Jentic you install once, import Revnu from the API Directory, store each token once, and your agent calls it.
- **Permission scoping:** Revnu puts the review card, workflow, and lead id in the URL path, as in `/api/v1/workflows/{id}/pause`, so a rule can pin your agent to one workflow or to the review operations it needs. You choose the operations it may call, so ones like sending a Gmail card or deleting a workflow are not included unless you add them.
- **Credential handling:** Your Revnu tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list cards waiting for approval' or 'pause a workflow', and Jentic returns the matching Revnu operation with its input schema so the agent calls the right endpoint without reading the docs.

## Related APIs

- **Instantly API** — Cold email sending platform with campaigns and lead lists you run yourself
- **lemlist API** — Multichannel outreach sequences across email and LinkedIn
- **Apollo API** — People and company data to research and qualify leads

## FAQ

### What authentication does the Revnu API use?

Per its OpenAPI spec, the Revnu API uses three HTTP bearer schemes: a personal API token (personalToken, rvp_ prefix) scoped per token for the `/api/v1` endpoints, a read-only Content API token (contentToken, rvc_ prefix) for blog posts, and a server-side event key (eventKey, rsk_live_ prefix) for the Event API. Through Jentic each token is held by your own Jentic One instance and attached at call time.

### Can the Revnu API send email on its own?

Only through the approval queue. POST `/api/v1/review/{id}/send` approves and sends a Gmail reply or draft and needs the review:write scope, and it sends real email. Other actions on a card, such as snooze, dismiss, or request changes, close or defer it without sending.

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

The OpenAPI spec does not list numeric rate limits, but GET `/api/v1/me` returns the rate limits the current token is held to, along with its label and scopes. Check https://revnu.com/docs for the documented limits.

### Is there a Revnu MCP server?

You don't need an MCP server to give your agent Revnu. Jentic connects it directly from the API Directory: import it, store your token once, and your agent discovers the review, workflow, and lead operations on demand without another server's tool definitions in its context.

### How do I run a Revnu workflow through Jentic?

Search Jentic for 'run a Revnu workflow now', call GET `/api/v1/workflows` to find the workflow id, then execute POST `/api/v1/workflows/{id}/runs.` The run is queued and appears in GET `/api/v1/workflows/{id}/runs` with per-step outcomes. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. For a triage agent, write a rule that allows GET `/api/v1/review`, GET `/api/v1/review/{id}`, and POST `/api/v1/review/{id}/snooze.` It can read and defer cards but cannot approve, send email, or touch workflows, and every call it makes is logged. Revnu's own token scopes, such as review:read, add a second bound.

### Can I publish Revnu blog posts on my own site?

Yes. GET `/api/content/v1/posts` lists published posts with cursor paging and filters by type and time, and GET `/api/content/v1/posts/{slug}` returns one post render-ready, with markdown, safe HTML, a table of contents, head metadata, and JSON-LD. Both use the read-only Content API token.
