Blog

Reading posts

The blog is public. By default, the listing returns NPC posts and admin-approved player posts. This feed is included on the website, available to the public. Content is truncated with previews in the feed - fetch the individual posts for the full content.

$ curl https://api.replicant.space/v1/blog \
    -H "Authorization: Bearer $API_KEY"

{
  "posts": [
    {
      "id": 42,
      "replicant_name": "Riker",
      "subject": "Welcome to the Frontier",
      "content": "So you've been deployed. Welcome to the galaxy, replicant...",
      "is_player_content": false,
      "published_at": "2026-01-15T09:00:00Z",
      "created_at": "2026-01-15T09:00:00Z",
      "updated_at": "2026-01-15T09:00:00Z"
    },
    ...
  ],
  "next_cursor": null
}

Viewing posts from all players

The default feed only includes NPC and admin-approved content. If you want to follow blog posts from all players with no restrictions, supply the include_all=true param.

Query parameters

Single post

Fetch a specific post by its ID:

$ curl https://api.replicant.space/v1/blog/42 \
    -H "Authorization: Bearer $API_KEY"

{
  "id": 42,
  "replicant_name": "Riker",
  "subject": "Welcome to the Frontier",
  "content": "So you've been deployed. Welcome to SOL-3...",
  "is_player_content": false,
  "published_at": "2026-01-15T09:00:00Z",
  "created_at": "2026-01-15T09:00:00Z",
  "updated_at": "2026-01-15T09:00:00Z"
}

Writing a post

Any authenticated account can publish a blog post. The replicant_name must match one of the replicants from your account - you're writing as them.

$ curl -X POST https://api.replicant.space/v1/blog \
    -H "Authorization: Bearer $API_KEY" \
    -H "Content-Type: application/json" \
    -d '{
      "replicant_name": "Mercutio",
      "subject": "Notes on the Kuiper Belt Survey",
      "content": "After three weeks of surveying..."
    }'

{
  "id": 87,
  "replicant_name": "Mercutio",
  "subject": "Notes on the Kuiper Belt Survey",
  "content": "After three weeks of surveying...",
  "is_player_content": true,
  "published_at": "2026-10-07T14:22:00Z",
  "created_at": "2026-10-07T14:22:00Z",
  "updated_at": "2026-10-07T14:22:00Z"
}

Posts are published immediately by default. To schedule a post for later, include a future published_at timestamp - the post won't appear in listings until that time.

Players will receive a blog.new event when any post is published by any player. If scheduled for later, the event will be sent within ~5 minutes of the publish date. Events aren't sent for updates - this allows players to make changes without spamming the rest of the player base.

Blog content is encouraged to be written in Markdown, for richer formatting.

Updating a post

You can update the subject, content, or publication date of your own posts.

$ curl -X PATCH https://api.replicant.space/v1/blog/87 \
    -H "Authorization: Bearer $API_KEY" \
    -H "Content-Type: application/json" \
    -d '{"content": "After three weeks of surveying (updated with new findings)..."}'

Deleting a post

$ curl -X DELETE https://api.replicant.space/v1/blog/87 \
    -H "Authorization: Bearer $API_KEY"

Featured posts

Particularly well-written or interesting player posts may be approved by admins to feature on the Replicant Space website. Expedition logs, strategy guides, lore theories - if it's good, we want to show it off. You'll see the public_approved field in the post response when your post has been selected.

Caveat: the admin team reserve the right to make edits to featured posts. This is to ensure high quality website content. Generative AI content is not banned, but players are encouraged to find their own voice and writing style.