getIntegrationsTelegramLinkAuthWithHttpInfo method

Future<Response> getIntegrationsTelegramLinkAuthWithHttpInfo()

Telegram Login Widget return leg

Where Telegram's Login Widget sends the user with its signed authentication data. That data is verified against the bot token — this is the identity source, and it is the widget's signature rather than a code exchange — and the chat is confirmed to be bound to an org before the browser is handed to the Hanzo sign-in. Widget data is only accepted while it is fresh, so a captured sign-in blob cannot be replayed later even though its signature stays valid. This is one leg of a three-leg flow, and the legs are not interchangeable: a browser is expected to arrive here only from the leg before it. The link URL's state proves the prompt was server-minted and carries the CHAT it started from — it is provenance only, and it never decides which account gets linked. The account identity always comes from the platform's own verified sign-in and a host-bound cookie, so forwarding a link to someone else cannot bind their account, and a session lifted into another browser is refused rather than completed. Each link is single-use, and a deployment without linking configured answers 503.

Note: This method returns the HTTP Response.

Implementation

Future<Response> getIntegrationsTelegramLinkAuthWithHttpInfo() async {
  // ignore: prefer_const_declarations
  final path = r'/v1/integrations/telegram/link/auth';

  // ignore: prefer_final_locals
  Object? postBody;

  final queryParams = <QueryParam>[];
  final headerParams = <String, String>{};
  final formParams = <String, String>{};

  const contentTypes = <String>[];


  return apiClient.invokeAPI(
    path,
    'GET',
    queryParams,
    postBody,
    headerParams,
    formParams,
    contentTypes.isEmpty ? null : contentTypes.first,
  );
}