CleverReach REST API

Name: CleverReach REST API API
Brand: CleverReach REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingEmail Marketingoauth2120 EndpointsREST

For Agents

Operate CleverReach end-to-end — manage groups, receivers, segmentation filters, mailings, forms, and advanced campaign statistics across a v3 surface of 120 endpoints.

Quickstart

Get started with CleverReach REST API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"segment cleverreach receivers"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with CleverReach REST API API.

Segment recipients with group-level filters and read filtered receiver counts and stats

Sync receivers in and out of groups, including order and event history per recipient

Manage forms attached to a CleverReach group for sign-up capture

Read advanced mailing statistics, including per-group performance breakdowns

GET STARTED

Start building with CleverReach REST API API

Explore with Jentic

View OpenAPI Document

Use for: I need to build a segment of CleverReach receivers with a filter, Get advanced statistics for a CleverReach group, Find all receivers in a group that match a saved filter, List the orders attached to a specific CleverReach receiver

Not supported: Does not handle SMS, push notifications, or transactional email delivery — use for CleverReach marketing list, segmentation, and mailing operations only.

Jentic publishes the only available OpenAPI document for CleverReach REST API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for CleverReach REST API, keeping it validated and agent-ready. The CleverReach REST API is the full v3 surface for CleverReach's email marketing platform, with 120 endpoints covering clients, groups, receivers, mailings, forms, attributes, filters, advanced statistics, and the blacklist. It exposes much deeper coverage than the slim cleverreach-api spec — including segmentation filters, group-level orders and events, form management, and client-level limits and plan data. Agents can use it to drive end-to-end email marketing operations including segmentation, campaign release, and analytics.

Use Cases

Patterns agents use CleverReach REST API API for, with concrete tasks.

★ Behavioural Segmentation and Targeted Sends

Build dynamic segments inside CleverReach by saving group-level filters and reading the resulting receiver lists and stats before triggering a targeted mailing. The /v3/groups/{group_id}/filters family of endpoints lets an automation create, count, and read filtered receivers, which feeds straight into a targeted send. Standing up a basic segmentation flow takes a day or two of integration work.

Create a filter on group_id 1234 that selects receivers with a specific tag, read /v3/groups/1234/filters/{filter_id}/count, and confirm the segment size before releasing a mailing

Receiver Order and Event History

Pull per-receiver order and event histories from CleverReach to power a personalised email or to feed a downstream CRM. The /v3/groups/{group_id}/receivers/{pool_id}/orders and /events endpoints expose this data per recipient, which is useful for transactional re-engagement campaigns and lifecycle automation. A working sync job takes under a day.

Fetch /v3/groups/1234/receivers/{pool_id}/orders for a specific receiver and surface the order count back to the caller

Sign-Up Form Management

Read and manage the sign-up forms attached to CleverReach groups so that an external site builder or CMS can render or update them programmatically. The /v3/groups/{id}/forms endpoint exposes the form metadata, which is enough to drive an embedded sign-up widget. A simple integration takes a few hours.

List forms for group_id 1234 via /v3/groups/1234/forms and return the form ids and names

Agent-Driven CleverReach Operations via Jentic

Hand CleverReach to an AI agent through Jentic so a marketing operator can describe an outcome — 'segment last month's bouncers and remove them' — and have the agent compose the right calls. Jentic isolates the OAuth credentials and surfaces only the relevant operations for the intent. A working integration takes well under an hour.

Search Jentic for 'segment cleverreach receivers', load the filter creation operation, and execute it against group_id 1234

Key Endpoints

120 endpoints — jentic publishes the only available openapi specification for cleverreach rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v3/groups/{group_id}/filters/{filter_id}/receivers

List receivers matching a saved filter

GET

/v3/groups/{group_id}/advancedstats

Read advanced statistics for a group

GET

/v3/groups/{group_id}/receivers/{pool_id}/orders

List orders for a receiver

GET

/v3/groups/{group_id}/receivers/{pool_id}/events

List events for a receiver

POST

/v3/blacklist

Add an email address to the blacklist

GET

/v3/clients/{id}/limits

Read account limits for a client

GET

/v3/groups/{group_id}/filters/{filter_id}/receivers

List receivers matching a saved filter

GET

/v3/groups/{group_id}/advancedstats

Read advanced statistics for a group

GET

/v3/groups/{group_id}/receivers/{pool_id}/orders

List orders for a receiver

GET

/v3/groups/{group_id}/receivers/{pool_id}/events

List events for a receiver

POST

/v3/blacklist

Add an email address to the blacklist

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

CleverReach OAuth 2.0 client credentials and access tokens are stored encrypted in the Jentic vault. Agents receive scoped execution handles — the client secret never enters the agent context.

Intent-based discovery

Agents search by intent (e.g., 'segment cleverreach receivers') and Jentic returns the matching CleverReach v3 operation with its input schema, so the agent calls the right endpoint without browsing 120 paths.

Time to first call

Direct CleverReach v3 integration: 2-4 days for OAuth, segmentation, and forms wiring. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

CleverReach API (slim)

A 19-endpoint subset of the CleverReach v3 API focused on the most common operations

Use the slim cleverreach-api spec when only the core upsert/release/blacklist operations are needed; use this main spec for segmentation, forms, and analytics

Alternative

Mailchimp Marketing API

US-hosted email marketing platform with deeper journey tooling

Choose Mailchimp for US-based customers or audiences requiring its journey builder; CleverReach is preferred for German/European data residency

Complementary

Mandrill API

Transactional email delivery service

Pair Mandrill with CleverReach when transactional email needs to flow through a separate provider from marketing email

FAQs

Specific to using CleverReach REST API API through Jentic.

Why is there no official OpenAPI spec for CleverReach REST API?

CleverReach does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CleverReach REST API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the CleverReach REST API use?

The CleverReach REST API uses OAuth 2.0 against rest.cleverreach.com. You exchange your client credentials for an access token and pass it as a bearer token in the Authorization header. Through Jentic, the OAuth client secret is held in the Jentic vault and never exposed to the agent context.

Can I build receiver segments with the CleverReach REST API?

Yes. Group-level filters at /v3/groups/{group_id}/filters allow you to create and store filter definitions, count matched receivers via /count, and pull the list via /receivers — which is enough to drive a targeted send.

Can I read per-receiver order and event history?

Yes. /v3/groups/{group_id}/receivers/{pool_id}/orders and the matching /events endpoint return the orders and tracked events attached to a receiver, which supports lifecycle and re-engagement campaigns.

What are the rate limits for the CleverReach REST API?

CleverReach does not document fixed numeric rate limits in the public spec. In practice, keep batch operations under a few hundred receivers per call and avoid tight polling loops on /v3/clients/{id}/contingent — once per minute is typically enough.

How do I segment a CleverReach list through Jentic?

Run pip install jentic, search for 'segment cleverreach receivers', load the filter creation operation, and execute it against the target group_id. Jentic handles the OAuth token exchange and returns the API response.