dataz.md
Log in Get started

Telegram API reference

Check whether the Telegram client is configured and authorized.

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

Purpose

GET/status

Check whether the Telegram client is configured and authorized.

Category: System 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 Telegram account.

Read the gateway authentication tutorial.

Parameters

NameInRequiredType / constraints
No parameters documented for this endpoint.

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}/status"

Response schema

Documented responses
200Response model: StatusResponseStatusResponse

Response example

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

{
  "ready": true,
  "status": "connected",
  "user_id": "123456789012345678",
  "username": "example_user",
  "uptime": 120.5
}

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

  • This endpoint does not expose cursor pagination in its current public contract.
  • 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.