CleverReach API

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

★ Only Publicly Available OpenAPI DocumentMarketingEmail Marketingoauth219 EndpointsREST

For Agents

Run CleverReach email marketing operations — upsert recipients into groups, release or stop mailings, validate addresses, and check client account contingents.

Quickstart

Get started with CleverReach 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:
"release a cleverreach mailing"

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

Capabilities

What an agent can do with CleverReach API API.

Upsert receivers into a CleverReach group with bulk operations on the upsertplus endpoint

Clear all receivers from a group or fetch the current group membership

Release a prepared mailing or stop one mid-send via mailing actions

Validate email addresses against the CleverReach blacklist before importing

GET STARTED

Start building with CleverReach API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for CleverReach API, keeping it validated and agent-ready. The CleverReach API powers email marketing automation for the European-hosted CleverReach platform, exposing operations to manage client accounts, recipient groups, individual receivers, mailings, and the global blacklist. It uses OAuth 2.0 against rest.cleverreach.com/v3 and covers the core lifecycle of building a list, validating addresses, releasing campaigns, and reading receiver counts. Agents can use it to upsert subscribers, trigger campaign sends, and query plan or contingent state for a client.

Use Cases

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

★ Subscriber List Sync from a CRM

Keep a CleverReach group in sync with a source-of-truth CRM by upserting receivers in bulk. The /groups/{group_id}/receivers/upsertplus endpoint accepts batches of recipients with attributes and updates existing records or creates new ones in a single call. A typical sync job runs nightly and takes a few hours to wire up against the CleverReach OAuth flow.

Upsert 200 receivers from a CSV into CleverReach group_id 1234567 using /groups/1234567/receivers/upsertplus and confirm the response counts the inserts and updates

Triggered Campaign Release

Trigger a CleverReach mailing to release on a schedule or in response to a business event. The /mailings/{id}/release endpoint kicks off the send for a prepared mailing, while /mailings/{id}/stop allows pulling the brake mid-send if a problem is detected. Integration is straightforward — under a day for a single mailing trigger.

Release CleverReach mailing id 987654 and verify the response confirms the mailing has moved into a sending state

Pre-Send Email Hygiene

Reduce bounce rates by validating email addresses against the CleverReach blacklist before importing them or releasing a campaign. The /blacklist/validate endpoint checks individual addresses, and /receivers/bounced returns the current bounced recipients for ongoing list cleaning. This pattern can be wired into a sign-up flow in a few hours.

Validate the address 'user@example.com' against /blacklist/validate and only call /groups/1234567/receivers/upsertplus if the address is clean

Agent-Driven Email Operations via Jentic

Expose CleverReach to an AI agent through Jentic so that an internal operator can ask the agent to release a campaign, sync a list, or check a client's contingent in natural language. Jentic stores the OAuth client credentials and surfaces only the relevant CleverReach operations for each intent. A working integration takes well under an hour.

Search Jentic for 'release a cleverreach mailing', load the schema for /mailings/{id}/release, and execute it with id=987654

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/groups/{group_id}/receivers/upsertplus

Bulk upsert receivers into a group

POST

/mailings/{id}/release

Release a prepared mailing

POST

/mailings/{id}/stop

Stop an active mailing

POST

/blacklist/validate

Validate an address against the blacklist

GET

/receivers/bounced

List bounced receivers

GET

/clients/{id}/contingent

Read remaining send contingent for a client

POST

/groups/{group_id}/receivers/upsertplus

Bulk upsert receivers into a group

POST

/mailings/{id}/release

Release a prepared mailing

POST

/mailings/{id}/stop

Stop an active mailing

POST

/blacklist/validate

Validate an address against the blacklist

GET

/receivers/bounced

List bounced receivers

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., 'release a cleverreach mailing') and Jentic returns the matching CleverReach operation with its input schema, so the agent calls the right endpoint without browsing the v3 reference.

Time to first call

Direct CleverReach integration: 1-2 days for OAuth setup, batch upsert payload shaping, and error handling. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Mailchimp Marketing API

US-hosted email marketing platform with deeper automation and template tools

Choose Mailchimp when the customer is US-based or wants advanced journeys; CleverReach is preferred for German/European data residency

Complementary

Mandrill API

Transactional email delivery layer from Mailchimp

Pair Mandrill (or a transactional ESP) with CleverReach when transactional and marketing email need to flow through different channels

Alternative

SendGrid Marketing Campaigns Single Sends

Twilio SendGrid's marketing campaign management API

Choose SendGrid when the team already runs transactional email through SendGrid and wants a single vendor

FAQs

Specific to using CleverReach API API through Jentic.

Why is there no official OpenAPI spec for CleverReach API?

CleverReach does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CleverReach 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 API use?

The CleverReach API uses OAuth 2.0 against rest.cleverreach.com/v3. You exchange your client credentials for an access token and pass it in the Authorization header. When called through Jentic, the OAuth client secret is held in the Jentic vault and never exposed to the agent context.

Can I bulk import subscribers with the CleverReach API?

Yes. The /groups/{group_id}/receivers/upsertplus endpoint accepts a batch of receivers with attributes and inserts new records or updates existing ones in a single call, which is the recommended path for syncing a list from an external source.

Can I release or stop a campaign programmatically?

Yes. /mailings/{id}/release triggers a prepared mailing to send, and /mailings/{id}/stop halts an active send. These are the two control endpoints you need for an automated send pipeline.

What are the rate limits for the CleverReach API?

CleverReach does not document fixed numeric rate limits in the public spec. Practical guidance is to keep upsert batches reasonable (a few hundred receivers per call) and avoid tight polling loops on /clients/{id}/contingent — once per minute is typically sufficient.

How do I send a campaign through Jentic?

Run pip install jentic, search for 'release a cleverreach mailing', load the operation against /mailings/{id}/release, and execute it with the target mailing id. Jentic handles the OAuth token exchange and returns the API response.