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

# CleverReach APIs

CleverReach is a European-hosted email marketing platform. Its APIs let you manage recipient groups and receivers, build segmentation filters, upsert and clean subscriber lists, release or stop mailings, validate addresses against the blacklist, manage sign-up forms, and read client-level plan, contingent, and campaign statistics. Jentic publishes and maintains the OpenAPI specifications for both CleverReach surfaces so agents can drive list, segmentation, and mailing operations through structured tooling.

## For AI agents

An agent can run end-to-end CleverReach email marketing across two v3 surfaces: sync and segment receivers in groups, upsert subscribers in bulk, release or stop mailings, validate addresses against the blacklist, manage sign-up forms, and read advanced group statistics plus client plan and contingent data.

## Scope

Use for: Managing CleverReach email marketing: group and receiver sync, segmentation filters, mailing release and stop, blacklist validation, sign-up forms, and campaign statistics.

Not supported:
- SMS messaging
- push notifications
- transactional email delivery
- landing page hosting

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| CleverReach REST API | marketing | 120 | Operate CleverReach end-to-end - manage groups, receivers, segmentation filters, mailings, forms, and advanced campaign statistics across a v3 surface of 120 endpoints. |
| CleverReach API | marketing | 19 | Run CleverReach email marketing operations - upsert recipients into groups, release or stop mailings, validate addresses, and check client account contingents. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Full email marketing operations including segmentation, forms, and analytics | main | The main REST API exposes the full 120-endpoint v3 surface, including group filters, sign-up forms, per-receiver order and event history, and advanced statistics. |
| Core list, mailing, and hygiene operations only | cleverreach-api | The slim 19-endpoint spec covers the common lifecycle: bulk receiver upsert, mailing release and stop, blacklist validation, and client contingent checks. |
| Bulk subscriber upsert into a group | cleverreach-api | The slim spec centers on the upsertplus batch endpoint for syncing a list from an external source without the wider surface. |
| Building and reading segmentation filters | main | Group-level filter endpoints for creating, counting, and reading filtered receivers exist only on the full REST API. |

## Cross-API use cases

### Segment on the full API, send on the slim API

Build a targeted audience with the main API's group-level filters, confirm the matched receiver count, then release the campaign through the slim API's mailing control endpoints. This splits the richer segmentation surface from the leaner send-and-stop path used in an automated pipeline.

Example prompt: Create a filter on group_id 1234 with the main API, read its receiver count, then release the prepared mailing with the cleverreach-api release endpoint

### Sync and clean a list, then read campaign results

Upsert subscribers in bulk and validate them against the blacklist through the slim API, then pull advanced per-group statistics from the main API after the campaign runs. This covers the full loop from list hygiene to post-send analytics.

Example prompt: Validate addresses and upsert receivers into a group with cleverreach-api, then read `/v3/groups/{group_id}/advancedstats` with the main API

### Enrich receiver records, then trigger lifecycle sends

Read per-receiver order and event history and configure custom group attributes with the main API, then trigger a re-engagement mailing through the slim API's release endpoint. This links behavioural data on the full surface to campaign control on the lean one.

Example prompt: Fetch a receiver's orders and events via the main API, then release a matching mailing with the cleverreach-api release endpoint

## Why Jentic

- **Setup:** Wiring CleverReach by hand means running its OAuth 2.0 flow and threading group, filter, mailing, and receiver ids through calls to rest.cleverreach.com across two specs. With Jentic you install once, add CleverReach from the Jentic API Directory, store the credential once, and your agent calls either surface.
- **Permission scoping:** CleverReach puts group id, pool id, and mailing id in the URL path, so your own rules can pin an agent to a single group and a specific set of operations. Reading a group's stats can be allowed while writing to the blacklist or releasing a mailing stays out unless you add it.
- **Credential handling:** Your CleverReach OAuth credential 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 the Jentic directory by intent such as 'segment cleverreach receivers' or 'release a cleverreach mailing', and Jentic returns the matching operation with its input schema, so the agent picks the right endpoint across both specs without browsing the reference docs.

## Related vendors

- **Mailchimp** — US-hosted email marketing platform with deeper journey tooling; an alternative when European data residency is not required.
- **Mandrill** — Transactional email delivery service that pairs with CleverReach when transactional and marketing email flow through separate providers.
- **SendGrid** — Marketing and transactional email platform; an alternative for teams that want a single vendor across both email types.

## FAQ

### What is the difference between the two CleverReach APIs in this directory?

The main REST API is the full v3 surface with 120 endpoints, covering segmentation filters, sign-up forms, per-receiver order and event history, and advanced statistics. The cleverreach-api spec is a slim 19-endpoint subset focused on the common lifecycle: bulk receiver upsert, mailing release and stop, blacklist validation, and client contingent checks. Use the slim spec when you only need core operations and the full spec when you need segmentation, forms, or analytics.

### Do both CleverReach APIs share the same credential?

Yes. Both authenticate with OAuth 2.0 against rest.cleverreach.com, so one CleverReach OAuth credential works across both surfaces. You do not need separate credentials for the slim and full specs.

### Why does Jentic publish the CleverReach specs?

CleverReach does not publish an OpenAPI specification for either surface. Jentic generates and maintains both specs so that agents and developers can call CleverReach through structured tooling. They are validated against the live API and kept up to date.

### Can an agent segment a list and send a campaign end to end?

Yes. An agent can build a segment with the main API's group-level filters, confirm the matched receiver count, and then release the mailing through either surface. This lets a single agent handle the full flow from audience building to campaign send.

### Is CleverReach suitable for European data residency needs?

CleverReach is a German-hosted email marketing platform, which is a common reason teams choose it over US-hosted alternatives when subscriber data needs to stay in Europe. Both APIs operate against the same European-hosted infrastructure.

### What email operations are out of scope for these APIs?

These APIs handle marketing list, segmentation, and mailing operations. They do not cover SMS messaging, push notifications, or transactional email delivery, which would need a separate provider paired alongside CleverReach.