# discourse.latest_posts

**stable** **Advanced**

Latest posts across a Discourse forum.

`GET /v1/discourse/latest_posts`

## What you get

A list of Discourse results in Onekey's unified shape, in `data` (an array). An empty array is a normal, successful answer and is charged like any other; a source that reports "nothing found" as an error returns a free `404 not_found` instead.

## What it costs

- **Advanced · 5 credits** for a fresh fetch, charged only when it succeeds.
- **Free when served from cache (0.2 credit for a cached response over 100 KB).**
- **Free** if the request is invalid (never charged) or the source fails or reports not found (refunded).

## Parameters

| Name | Type | Required | Default | What it is | Constraints |
| --- | --- | --- | --- | --- | --- |
| `instance` | string | no | - | Known Discourse forum (allowlisted), default meta.discourse.org | max 253 chars; must match `[a-z0-9.-]{3,253}`; trimmed, lowercased |

## Request

```bash
curl "https://api.onekey.dev/v1/discourse/latest_posts" \
  -H "x-api-key: YOUR_API_KEY"
```

```python
import requests

res = requests.get(
    "https://api.onekey.dev/v1/discourse/latest_posts",
    params={},
    headers={"x-api-key": "YOUR_API_KEY"},
)
body = res.json()

if body["success"]:
    print(body["data"])
else:
    print(body["error"]["code"], body["error"]["message"])
```

```javascript
const params = new URLSearchParams({});
const res = await fetch(`https://api.onekey.dev/v1/discourse/latest_posts?${params}`, {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const body = await res.json();

if (body.success) console.log(body.data);
else console.error(body.error.code, body.error.message);
```

## Recorded response

A real Discourse response, recorded and returned in Onekey's shape. Fields the platform does not provide are `null`.

```json
{
  "success": true,
  "data": [
    {
      "content": {
        "id": "2044803",
        "text": "We were using this over the weekend to good effect One bug / unexpected feature we found is that the system supports stereo mics. Normally, on web conferencing software, the left channel and right channel are downmixed to mono since mono mic hardware are typically used for capturing this sort of audio. (This also theoretically reduces bandwidth usage). The Discourse solution currently transmits full stereo mics. However, some mics will only output to one channel and leave the other empty. (Maybe this is just more typical for prosumer audio interfaces that have multiple inputs, but I imagine some cheap mics might end up doing this, too). This results in the listeners only hearing that speaker in the left or right ear. I actually did not realize this, but apparently Mumble, discord, nextcloud, jitsi, games, etc all downmix to mono. So, I would recommend defaulting to downmix the mic audio stream (not the screenshare audio stream which should be a separate set of channels) to mono. Generally speaking, there’s probably few situations the user would actually want a wide field of view to capture audio during a call – maybe if a music band was using it to stream to their fans, perhaps. In that case, if the user specifically has and wants to use a wide-field stereo mic, let them enable it vi",
        "createdAt": "2026-09-28T19:28:15Z",
        "slug": "voice-discord-style-voice-and-video-rooms-now-bundled-with-discourse"
      },
      "author": {
        "username": "SkyeDragon",
        "displayName": "Skye"
      },
      "ext": {
        "topicId": "411337",
        "postNumber": 71
      },
      "engagement": {
        "comments": 0,
        "likes": null
      }
    },
    {
      "content": {
        "id": "2044796",
        "text": "It would be good if you could select from the various trust levels and groups.",
        "createdAt": "2026-09-28T19:03:03Z",
        "slug": "regular-mode-for-admins-and-moderators-e-g-something-like-sudo"
      },
      "author": {
        "username": "Jonathan5",
        "displayName": ""
      },
      "ext": {
        "topicId": "211617",
        "postNumber": 49
      },
      "engagement": {
        "comments": 0,
        "likes": null
      }
    }
  ],
  "metadata": {
    "platform": "discourse",
    "endpoint": "latest_posts",
    "cached": false,
    "stale": false,
    "age_s": 0,
    "fetched_at": "2026-01-01T12:00:00+00:00",
    "credits_charged": 5,
    "request_id": "7f3a9c2e5b1d4c8fa2e6d0b9c4f18e37"
  },
  "error": null
}
```

## Field mapping

How this endpoint's source fields become Onekey's [unified schema](https://onekey.dev/docs/schema.md). Fields the source lacks come back as `null`.

| Source path | Onekey field | Transform |
| --- | --- | --- |
| `id` | `content.id` | `toString` |
| `username` | `author.username` | - |
| `name` | `author.displayName` | - |
| `cooked` | `content.text` | `stripHtml` |
| `created_at` | `content.createdAt` | `toIsoDate` |
| `topic_id` | `ext.topicId` | `toString` |
| `reply_count` | `engagement.comments` | `toNumber` |
| `like_count` | `engagement.likes` | `toNumber` |
| `post_number` | `ext.postNumber` | `toNumber` |
| `topic_slug` | `content.slug` | - |

## Caching and freshness

- Fresh for about 30 seconds. Repeat calls in that window are served from cache and are free.
- Between 30 seconds and 5 minutes the cached copy is still served instantly and marked `stale: true` while Onekey refreshes it in the background.
- If the source is down when a refresh is needed, the last copy can be served for up to 1 hour more (marked stale).
- A "not found" is remembered for 1 minute and is free.
- The cache is shared across all customers, which is what keeps repeat calls cheap.

## What can go wrong

| Status | Code | What to do |
| --- | --- | --- |
| 401 | `unauthorized` | Check the `x-api-key` header. |
| 402 | `insufficient_credits` | [Add credits](https://onekey.dev/pricing); your balance must cover the price. |
| 404 | `not_found` | Unknown endpoint path. |
| 422 | `invalid_params` | Fix the parameters using the table above. Free. |
| 429 | `rate_limited` | Wait `Retry-After` seconds, then retry. |
| 502 | `upstream_error` | The source failed. Refunded; retry with backoff. |

See [Errors](https://onekey.dev/docs/errors.md) for the full list and retry guidance.

Status: stable (verified against the live source).