---
title: "Create blog post (service role only)"
method: POST
path: "/blog/posts"
tags: ["Blog"]
---

# Create blog post (service role only)

`POST /blog/posts`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/blog/posts`
- Auth: HTTP bearer

**Requires ServiceRole authentication.** This endpoint is only accessible to platform administrators with the Supabase service role key. Regular API keys and user tokens cannot access this endpoint.

Create a new blog post.

## Request body

- object
  - `agent_id` string, required
  - `slug` string, required
  - `title` string, required
  - `subtitle` string
  - `body` string, required
  - `tags` string[]
  - `investigation_session_id` string
  - `trace_ids` string[]
  - `status` 'draft' | 'published'

## Response `201`

Post created

- object

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `409`: Resource conflict — the request cannot proceed because of a current state conflict (e.g., resource already exists, version mismatch, in-flight idempotency key with a different body).
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)