Resolve a Telegram ID to an Internal ID
GET/v1/utils/resolve_telegram_id
Resolve telegram_id to internal_id
Request
Responses
- 200
- 400
- 401
- 402
- 403
- 404
- 412
- 426
- 429
- 503
Resolved id
Response Headers
Milli-credits charged for this successful request. Present for Credits API keys.
Remaining milli-credit balance after this request. Present for Credits API keys.
Bad Request: The request sent to the server is invalid.
Request parameters are missing, incorrect, or in the wrong format.
Unauthorized: The provided API key is invalid or absent.
Provided in the request API key is not valid or is missing.
Payment Required: Not enough credits to perform this request.
The plan allows this call but the credit balance does not cover it. Top up credits and retry. Amounts are in milli-credits (1 credit = 1000).
Forbidden: Access to this resource is not allowed.
User does not have permission to access this feature.
Not Found: Requested resource could not be found on the server.
Specific resource with the provided ID cannot be found.
Inactive Subscription: The user's subscription is not currently active.
User subscription has expired or is otherwise inactive.
Quota Reached: The user's subscription limit has been reached.
User has exceeded their monthly limit for unique channels or total requests.
For higher limits please contact us via Telegram @telemetrio_contact or write to contact@telemetr.io.
Too Many Requests: The request rate limit has been reached.
Retry after the interval indicated by the response headers.
Service Unavailable: Credit accounting is temporarily unreachable.
The request was refused rather than served without being billed. This is transient — retry with backoff.
Carries the standard message envelope, with a constant message: the underlying failure is ours and its text names internal machinery, so it is never forwarded.