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

# BlendDuck Public API

The BlendDuck Public API publishes a single logical post across multiple connected social channels and tracks how each one performed. It lists and disconnects workspace channels, uploads inspected media for posts, compares attributed social performance, and exposes each provider's posting capabilities. Workspace webhook endpoints report delivery events, with secret rotation, delivery history, test events, and safe replay of a failed delivery.

## For AI agents

Publish multi-target social posts and track their performance: create a logical post across connected channels, upload media, compare attributed analytics, and manage webhook endpoints across 25 endpoints.

## Scope

Does not design graphics, run paid ad campaigns, or manage direct messages. Use for publishing posts to connected social channels and tracking their performance only.

## Capabilities

- Publish a single logical post to multiple connected social channels at once
- List and disconnect the social channels in a workspace
- Compare attributed performance across your published posts
- Upload and reuse inspected media for posts
- Register webhook endpoints and inspect their delivery history
- Rotate a webhook signing secret and replay a failed delivery
- Read each provider's posting capabilities before composing a post

## Use cases

### Cross-channel publishing through Jentic

Let an agent post the same update everywhere at once. The agent composes one logical post and targets the connected channels, and BlendDuck fans it out to each provider. Through Jentic the post operation is discovered by intent and called with its input schema, so publishing across channels is a single step.

Example prompt: Create a multi-target post with POST `/api/v1/posts` targeting the connected channels

### Performance comparison

Measure which posts and channels are working without opening each platform's dashboard. The agent reads attributed social performance across published posts, so a reporting workflow can rank posts or flag underperformers.

Example prompt: Compare post performance with GET `/api/v1/analytics`

### Media upload and reuse

Attach images or video to a post from a managed media library. The agent uploads inspected media once and references it when composing a post, so the same asset can appear across channels without re-uploading.

Example prompt: Upload media with POST `/api/v1/media`, then reference it when creating a post with POST `/api/v1/posts`

### Webhook delivery monitoring

Keep an eye on post and channel events delivered to your own endpoint. The agent lists a webhook endpoint's delivery history and replays a failed delivery, so an integration recovers from a missed event without manual intervention.

Example prompt: List deliveries with GET `/api/v1/webhooks/{webhookEndpointId}/deliveries`, then replay a failed one with POST `/api/v1/webhooks/{webhookEndpointId}/deliveries/{webhookDeliveryId}/replay`

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v1/posts` | Create a logical multi-target post |
| GET | `/api/v1/posts` | List logical posts |
| GET | `/api/v1/analytics` | Compare attributed social performance |
| GET | `/api/v1/channels` | List workspace channels |
| POST | `/api/v1/media` | Upload inspected workspace media |
| POST | `/api/v1/webhooks` | Create a workspace webhook endpoint |
| GET | `/api/v1/webhooks/{webhookEndpointId}/deliveries` | List webhook delivery logs |
| GET | `/api/v1/providers` | List provider capabilities |

## Key resources

- **Posts** — Create, update, and delete logical multi-target posts
- **Channels** — List, read, and disconnect connected workspace channels
- **Media** — Upload, list, and read inspected workspace media
- **Webhooks** — Register endpoints, rotate secrets, and inspect and replay deliveries
- **Analytics** — Compare attributed performance across published posts

## 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:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 83 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 64 / 100
- **View full report:** https://jentic.com/apis/blendduck.com/blendduck/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 BlendDuck by hand means learning its bearer auth, the one-organization-per-key model, and its multi-target post and webhook delivery shapes. Through Jentic you install once, import BlendDuck from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** BlendDuck's key already scopes the agent to one organization, and ids like the webhook endpoint id travel in the URL path. You choose which operations your agent may call, so it can publish posts and read analytics while channel disconnection or webhook deletion stays out unless you add them.
- **Credential handling:** Your BlendDuck token 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 Jentic by intent such as 'publish a social post' or 'compare post performance', and Jentic returns the matching BlendDuck operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Sendible API** — Sendible schedules and publishes across many social networks with reporting; BlendDuck publishes a single logical post across connected channels with attributed analytics.
- **Late API** — Late is a developer-first social scheduling API; BlendDuck adds a workspace model with webhook deliveries and provider capability discovery.
- **Canva Connect API** — Canva designs and exports post visuals; BlendDuck publishes those assets across connected channels.

## FAQ

### What authentication does the BlendDuck Public API use?

The BlendDuck Public API authenticates with a bearer token per its OpenAPI spec, and the token selects the organization it acts on, so posts and media stay within that workspace. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time.

### Can I publish one post to multiple channels with the BlendDuck Public API?

Yes. Create a single logical post and BlendDuck fans it out to the connected channels you target, then list, update, or delete that logical post and read provider capabilities to see what each channel supports.

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

Yes. Write a rule that allows only post creation and analytics reads, so your agent can publish and measure posts but cannot disconnect channels or delete webhook endpoints unless you add those operations. BlendDuck carries a post's target channels in the request body, so rules bound which operations run, not which channel is reached.

### What are the rate limits for the BlendDuck Public API?

The OpenAPI spec does not specify rate limits. Check the BlendDuck documentation at https://blendduck.com for current limits before publishing at high volume.

### Is there a BlendDuck MCP server?

You don't need an MCP server to give your agent BlendDuck. Jentic connects it directly from the API Directory: import it, store your token once, and your agent runs the post, media, and analytics operations on demand. That also keeps extra tool definitions out of the agent's context.

### How do I publish a post to multiple channels with the BlendDuck Public API through Jentic?

Search Jentic for 'publish a post to multiple social channels' and it returns the BlendDuck post operation with its input schema. Your agent composes one logical post, targets the connected channels, and BlendDuck delivers it. To run it on your own infrastructure, install Jentic One from its GitHub repo.