Discord Get messages in a forum post | dataz.md API reference

Purpose

GET/forums/{forum_id}/posts/{post_id}/messages

Fetch message history from a forum post (thread).

forum_id: Discord forum channel ID
post_id: Discord post (thread) ID
limit: Number of messages to retrieve (1-1000)
before: Get messages before this message ID
after: Get messages after this message ID

Category: Messages Auth: Authorization bearer or X-API-Key Scope: read-only

Authentication

Send a tenant API key as Authorization: Bearer <key> or X-API-Key: <key>. Keep keys server-side and use the account slug for the connected Discord account.

Read the gateway authentication tutorial.

Parameters

NameInRequiredType / constraints

forum_id path required integer

post_id path required integer

limit query optional integer · default 100 · range 1–1000

before query optional integer · default null

after query optional integer · default null

Request example

Replace the tenant, account, and resource placeholders before running this read-only request.

curl --fail-with-body \
  -H "Authorization: Bearer ${DATAZ_API_KEY}" \
  "https://dataz.md/gateway/v1/{tenant_slug}/accounts/{account_slug}/forums/{forum_id}/posts/{post_id}/messages?limit=100"

Response schema

Documented responses

200Response model: List[Message]List[Message]

Response example

Representative JSON shape. The live response can include additional documented fields.

[
  {
    "id": "123456789012345678",
    "content": "Example message",
    "type": 0,
    "timestamp": "2026-01-01T00:00:00Z",
    "channelId": "123456789012345678",
    "author": {
      "id": "123456789012345678",
      "username": "example_user",
      "display_name": "Example User"
    }
  }
]

Errors

Common responses

401Missing or invalid tenant API key.authentication

403The tenant, account, or connected provider cannot access the requested resource.authorization

404The route or requested provider resource was not found.not found

422A path or query parameter is invalid.validation

429Rate limited; wait for the Retry-After interval before retrying.rate limit

Limits and pagination

Use limit to bound each response; it defaults to 100 and accepts 1–1000.
Use before to continue toward older records or after for incremental reads; store source IDs as cursors.
Provider or demo limits can return HTTP 429. Wait for the Retry-After interval before retrying.

Read-only notes

This reference page documents a public GET endpoint. Setup/token, AI, dev, internal, and mutating routes are excluded from static reference generation.