dataz.md
Log in Get started

Troubleshooting

Troubleshoot setup, gateway, and API calls.

Use these checks when onboarding, account activation, gateway authentication, or read-only endpoint calls do not behave as expected.

Get started Explore docs

Steps

  1. Confirm the workspace and provider account are activated in the portal.
  2. Confirm the route uses the account-specific gateway shape for multi-account tenants.
  3. Confirm the request includes either Authorization bearer auth or X-API-Key.
  4. Open provider-specific docs and verify the endpoint path, required path parameters, and query parameters.
  5. If data is missing, verify the connected account can read the source conversation, server, channel, or topic.

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}/...
Authorization: Bearer <key>
X-API-Key: <key>

Limitations

  • Do not put plaintext API keys in screenshots, issue reports, committed files, or browser-visible pages.
  • A 404 can mean the route is not public, the path is wrong, or the selected provider/account cannot expose that resource.
  • Setup/token, AI, dev, and internal routes are not public data gateway 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