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

# Sendible API

Sendible social media management API for managing posts, profiles, services, reports, and content. The API exposes 10 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create post, list posts. Covers 10 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for social media only.

## Capabilities

- Create post
- List posts
- Get post
- Update post
- Delete post

## Use cases

### Social Media Operations

Use the Sendible API to perform social media operations programmatically. The API provides 10 endpoints covering core functionality including create post, list posts, get post.

Example prompt: Call POST /posts to create post

### Automated Media Management

Automate media operations by combining multiple Sendible API endpoints. Agents can list posts and then get post in a single workflow.

Example prompt: Call GET /posts to list posts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Sendible API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'create post', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/posts` | Create post |
| GET | `/posts` | List posts |
| GET | `/posts/{postId}` | Get post |
| PUT | `/posts/{postId}` | Update post |
| DELETE | `/posts/{postId}` | Delete post |
| GET | `/services` | List services |
| GET | `/services/{serviceId}` | Get service |
| GET | `/reports` | List reports |

## Key resources

- **Media** — Operations related to Media
- **Posts** — Operations related to Posts
- **Reports** — Operations related to Reports
- **Services** — Operations related to Services

## 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:** 49 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/sendible.com/sendible/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 the Sendible API by hand means setting up its api_key query-parameter auth, appending the key to every request against api.sendible.com/api/v2, and handling status codes yourself. Through Jentic you install once, import the Sendible API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Sendible API puts the post id in the URL path (`/posts/{postId}`), so a rule can pin your agent to one post. You choose the operations it may call, so destructive ones like deleting or updating a post are not included unless you add them.
- **Credential handling:** Your Sendible API key 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 'schedule a social media post', and Jentic returns the matching Sendible operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook** — Alternative social media API
- **Twitter** — Alternative social media API
- **Linkedin** — Complementary social media API

## FAQ

### What authentication does the Sendible API use?

The Sendible API uses an API key passed in the `api_key` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create post with the Sendible API?

Yes. Use the POST /posts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

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

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create post through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create post'. Jentic returns the matching Sendible API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Sendible API have?

The Sendible API exposes 10 endpoints covering media, posts, reports operations.

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

Yes. Because Jentic One is self-hosted, you run it and your own rules decide which Sendible operations and credentials the agent can use. You can allow read-only calls like GET /posts, GET /services, and GET /reports while excluding write and destructive operations such as POST /posts, PUT `/posts/{postId}`, and DELETE `/posts/{postId}` unless you explicitly add them. Since the post id sits in the URL path (`/posts/{postId}`), a rule can also pin the agent to a single post.