dataz.md

Discord API reference

Search messages across Discord guilds

Crawlable reference for GET /messages/search through a dataz.md tenant gateway.

Purpose

GET/messages/search

Search accessible guilds with Discord's native message search.

Unscoped requests process four guilds at a time. Pass the opaque cursor returned by one page to resume at the next stable guild batch. The truncated flag and truncated_guilds identify result-limit truncation.

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
content query optional string · default null
author_id query optional integer · default null
author_name query optional string · default null
guild_id query optional integer · default null
channel_id query optional integer · default null
before query optional integer · default null
cursor query optional string · default null
limit query optional integer · default 50 · range 1–100

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}/messages/search?limit=100"

Response schema

Documented responses
200Response model: JSON responseobject

Response example

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

{
  "results": [
    {
      "id": "123456789012345678",
      "channel_id": "123456789012345670",
      "guild_id": "123456789012345600",
      "content": "Example matching message",
      "author_id": "123456789012345679",
      "author_username": "example_user",
      "author_display_name": "Example User"
    }
  ],
  "authors": [
    {
      "id": "123456789012345679",
      "username": "example_user",
      "display_name": "Example User"
    }
  ],
  "searched": [
    "123456789012345600"
  ],
  "skipped": [],
  "cursor": null,
  "partial": false
}

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 50 and accepts 1–100.
  • 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.

Related tutorials

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.