Telegram Compatibility endpoint mapping Telegram contacts to friends.

Purpose

GET/existing_friends

Compatibility endpoint mapping Telegram contacts to friends.

Category: Contacts 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}/existing_friends"

Response schema

Documented responses

200Response model: List[Friend]List[Friend]

Response example

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

[
  {
    "user_id": "123456789012345678",
    "name": "Ada Lovelace"
  }
]

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.

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.