Posts

GET /api/v1/posts

List your posts by lifecycle status. Query params

Param	Type	Default	Values
`status`	string	`scheduled`	`draft`, `scheduled`, `published`
`limit`	int	`20`	Clamped 1–100
`offset`	int	`0`	Pagination

curl "https://api.magicpost.in/api/v1/posts?status=scheduled&limit=10" \
  -H "Authorization: Bearer mp_xxx"

Response

{
  "status": "scheduled",
  "limit": 10,
  "offset": 0,
  "posts": [
    {
      "id": "uuid",
      "post_content": "Multiple\n\nline post.",
      "created_at": "2026-05-12T10:00:00Z",
      "date_post": "2026-05-20",
      "hour_post": "14:00",
      "schedule_date": "2026-05-20T12:00:00Z",
      "schedule_timezone": "Europe/Paris",
      "planified_post": true,
      "published_post": false,
      "linked_in_url_post": null,
      "word_count": 152,
      "type": "Actionable",
      "category": "Education",
      "approved": null
    }
  ]
}

GET /api/v1/posts/<post_id>

Fetch one post in full. 404 if not owned by you.

curl https://api.magicpost.in/api/v1/posts/uuid \
  -H "Authorization: Bearer mp_xxx"

POST /api/v1/posts

Create a draft post. Body

{ "content": "Hello LinkedIn world\n\nThis is line 2." }

content (required) — post text. Line breaks (\n) are preserved verbatim and rendered on LinkedIn.

This REST endpoint creates text-only drafts. MCP clients that support chat file references can then call attach_media_to_post; otherwise add images, videos, polls and @mentions from the MagicPost web UI.

Response (HTTP 201)

{ "success": true, "post_id": "new-uuid", "created": true }

PATCH /api/v1/posts/<post_id>

Update the content of an existing post. Body

{ "content": "Updated text." }

Response

{ "success": true, "post_id": "uuid", "created": false }

Returns 404 if you don’t own the post (IDOR guard).

POST /api/v1/org/members/<member_user_id>/posts

Create a draft owned by a member of the caller’s organisation. The caller must be an organisation super_admin, and the target member must still belong to the same organisation.

curl -X POST \
  https://api.magicpost.in/api/v1/org/members/member-uuid/posts \
  -H "Authorization: Bearer mp_xxx" \
  -H "Content-Type: application/json" \
  -d '{"content":"A post drafted for this team member."}'

Response (HTTP 201)

{
  "success": true,
  "post_id": "new-post-uuid",
  "member_user_id": "member-uuid",
  "created": true
}

MCP clients should use create_member_post. To attach media, pass both the returned post_id and the same member_user_id to the appropriate media tool, then call schedule_member_post.

Overview

Endpoints

GET /api/v1/posts

GET /api/v1/posts/<post_id>

POST /api/v1/posts

PATCH /api/v1/posts/<post_id>

POST /api/v1/org/members/<member_user_id>/posts

​GET /api/v1/posts

​GET /api/v1/posts/<post_id>

​POST /api/v1/posts

​PATCH /api/v1/posts/<post_id>

​POST /api/v1/org/members/<member_user_id>/posts

GET /api/v1/posts

GET /api/v1/posts/<post_id>

POST /api/v1/posts

PATCH /api/v1/posts/<post_id>

POST /api/v1/org/members/<member_user_id>/posts