dataz.md
Log in Get started

Discord export

Export Discord data through read-only API calls.

Use dataz.md to fetch Discord data as JSON through GET endpoints, then save or index the responses in your own workflow.

Get started Explore docs

Steps

  1. Create or open a workspace with an activated Discord account slot.
  2. Create a tenant API key in the portal and copy the account-specific gateway URL.
  3. List guilds, choose a guild or channel, then page through the read-only message or member endpoints your workflow needs.
  4. Store responses in your destination system and keep source IDs so future fetches can reconcile changes.

Prerequisites

  • A dataz.md workspace with an activated account slot.
  • A tenant API key created in the portal.
  • Access to data the connected provider account can read.

API paths used

GET /v1/{tenant_slug}/accounts/{account_slug}/guilds
GET /v1/{tenant_slug}/accounts/{account_slug}/guilds/{guild_id}/channels
GET /v1/{tenant_slug}/accounts/{account_slug}/channels/{channel_id}/logs
GET /v1/{tenant_slug}/accounts/{account_slug}/forums/{forum_id}/posts

Limitations

  • This is an API-call workflow, not a packaged bulk-download workflow.
  • The connected account must already be able to read the guild, channel, DM, forum, or invite data.
  • The API does not send, edit, delete, react, join, run moderation actions, bot commands, webhook workflows, setup/token routes, or provider-account control routes.

Check the reference details.

Use the endpoint reference for parameters, response schemas, and tenant gateway notes.

Open docs Discord reference Telegram reference All tutorials