Build with the public API.

Returns recently published posts, newest first.

Query parameters

Response

{
  "data": [
    {
      "id": "abc",
      "url": "https://www.crowdwide.run.place/posts/66f1a2b3c4d5e6f7a8b9c0d1",
      "body": "Post text.",
      "type": "post",
      "author": { "_id": "...", "name": "...", "profilePicture": "..." },
      "community": { "_id": "...", "name": "...", "slug": "..." },
      "hashtags": ["example"],
      "media": [{ "url": "...", "kind": "image", "alt": "...", "caption": "..." }],
      "createdAt": "2026-09-15T03:00:00.000Z"
    }
  ],
  "nextCursor": "2026-09-14T18:22:00.000Z"
}

community is null for a post not in a community. nextCursor is the createdAt of the last item in data, or null when there isn't a next page (fewer results came back than limit asked for) - pass it as before on your next request to page through results.

Rate limit

120 requests per minute per client (standard RateLimit-* response headers). Exceeding it returns 429 with { "error": "Too many API requests. Try again shortly." }.

Privacy

Posts in a private community never appear here, for anyone, under any community filter value - there's no way to authenticate this endpoint, so it can't tell members from non-members and treats every private community as fully off-limits. Passing a private community's ID returns { "data": [], "nextCursor": null }, not an error - the endpoint doesn't reveal whether a given ID belongs to a private community, a nonexistent community, or a community with no posts yet.

Errors

A 500 with { "error": "Internal server error." } means something broke server-side (most often a database hiccup) - it does not mean your request was malformed. Malformed query parameters are silently ignored (e.g. an invalid community value is treated as "no filter") rather than rejected with a 400, so a typo in a param name or value just falls back to the default rather than erroring.

RSS feeds

Three RSS 2.0 feeds, all public, all read-only. Each entry links to the post's page on Crowdwide rather than embedding full rendered HTML.

Also public, not really "the API"

These aren't meant for programmatic consumption of post data - use /api/v1/posts or the RSS feeds for that.