Tools and REST API

Look up Content MCP tools, REST routes, pagination, idempotency, workflow steps and errors.

Copy page

Use the Content MCP tools through your agent, or call their REST routes from your code. Each tool and route uses the same handler, inputs and outputs.

The caller’s credentials establish identity and product access. Do not pass a product id or acting identity as a tool argument or request-body field.

Full generated schemas are in the MCP tool catalog and the Content REST reference.

Where to call

Send Content management requests to the platform API with a bearer credential:

The published /openapi.json defines this base URL and bearer authentication for the /content routes.

A raw API key is limited to its issued product. A session or exchanged token can select another product its owner belongs to. Before calling, read The REST API and keys for product selection and X-Product-Id behavior.

Posts

Channels

There is no create tool: channels are seeded, one per network.

Publications

Media

Metrics

Paging

Pass limit and offset as query parameters to list routes. Posts, channels, publications and media accept limit from 1 to 100 (default 50); metric series accept 1 to 500 (default 200). total counts all matching records before paging.

Idempotency

The following five operations accept an Idempotency-Key request header over REST. Reuse the key when retrying an unclear outcome to receive the first response instead of repeating the action:

• content_posts_create — POST /posts
• content_posts_submit — POST /posts/{id}/submit
• content_publications_schedule — POST /publications
• content_publications_publish — POST /publications/publish
• content_publications_cancel — POST /publications/{id}/cancel

Schedule and publish also accept an idempotencyKey field, stored on the publication. Reusing it returns the same publication, except when that publication failed or was cancelled: the key is then spent and returns 409 idempotency_key_spent. See Publications.

Errors

A 409 identifies a state or validation conflict. Examples include submitting without targets or required fields, approving a post outside pending_approval, editing scheduled or finished content, and acting on a finished publication. Reminding before the first reminder also conflicts.

Publication conflicts include already_scheduled, idempotency_key_spent, publication_in_flight, publication_changed and not_a_reminder_channel, plus target and variant validation codes. Duplicate and spent-key errors include the affected publicationId and scheduledAt. Read the record and follow the recovery guidance in Publications before retrying.

Using these tools from a workflow

Workflows expose the following steps. Approval remains a separate action for a person.

Use content/post.approved to resume after a person approves the version. content_posts_approve is not offered as a workflow step, so a drafting workflow cannot approve its own output.

Schedule and publish return a queued record. Match its id to publicationId in the later content/publication.settled event, then branch on status (published, failed or cancelled). Cancellation returns the cancelled record directly.

Clients

The published @lepsto/sdk 1.2.0 has no generated Content client or @lepsto/sdk/content import. Its generated namespaces are mail, realtime, support, tracking and users. Importing the package root does not add Content operations.

Use the MCP tools or call https://api.lepsto.com/content/… with an HTTP client and bearer credential. The SDK also exports a generic HTTP client, but no typed Content methods.

Choose retries according to the operation. Use Idempotency-Key on the five supported routes, inspect any Retry-After header returned, and read the publication after a state conflict before deciding whether to repeat the request.

Next steps

• Content REST reference: the generated schema for every route above.
• Posts: the state machine the 409 responses enforce.