eSeGeCe — Enterprise Communication Components for Delphi & .NET

WHAT IS IN THE PACK

Two Networks, Two Components

sgcSocial is a standalone package. It bundles the sgcWebSockets Core runtime it is built on, and every license ships with full source code, so the messaging flows step through in your own debugger.

2 Client components TsgcTDLib_Telegram and TsgcWhatsApp_Client, on one palette page.

2 Messaging networks Telegram through the official TDLib engine, WhatsApp through the Business Cloud API.

5 Target platforms Windows, macOS, Linux 64-bit, Android and iOS through native TDLib builds. The WhatsApp client is pure HTTPS and compiles everywhere.

1 Standalone installer The sgcWebSockets Core runtime, the TLS layer and the webhook server all ship inside the package.

100% Source code included Every license carries the full source of both components and the bundled runtime.

sgcSocial

Telegram and WhatsApp Business client components for Delphi and C++ Builder. A standalone package with the sgcWebSockets Core runtime bundled in, full source code, and royalty-free deployment.

Product overview See pricing →

TWO COMPONENTS

One Component per Network, One API Style

Drop a component on a form, set the credentials, wire the events, then call the send methods. The naming is consistent across both, so a support inbox, a notification pipeline or a chatbot reads the same whichever network it targets.

Telegram · TDLib

A Full Telegram Client, Users and Bots Alike

TsgcTDLib_Telegram drives the official TDLib engine, so it signs in as a real user account with phone authentication and the 2FA password step (OnAuthenticationCode, OnAuthenticationPassword), or as a bot with a token. SendTextMessage, SendPhotoMessage, SendDocumentMessage, SendMessageAlbum and SendInvoiceMessage cover the content types, with EditTextMessage and ForwardMessages behind them. Group, supergroup and secret chats, searches, inline and reply keyboards and payments are all typed methods and events, and incoming traffic arrives as OnMessageText, OnMessageDocument, OnMessagePhoto, OnMessageVideo, OnNewChat and OnNewCallbackQuery.

View the Telegram client →

WhatsApp Business

The Cloud API, Webhook Included

TsgcWhatsApp_Client talks to the WhatsApp Business Cloud API (the Meta Graph API) with a PhoneNumberId and a Token. Text, image, document, audio, video and sticker messages, SendFile* variants that upload local files, reactions, location and contact cards, interactive lists and buttons, and message templates with a language code. UploadMedia, DownloadMedia and DeleteMedia manage assets, MarkMessageRead keeps conversations tidy, and the built-in webhook endpoint (StartServer, OnBeforeSubscribe verification, OnMessageReceived, OnMessageSent) receives inbound traffic without an extra server.

View the WhatsApp client →

Use cases

Built for the Inbox

Customer support inboxes, order and delivery notifications, 2FA and alert delivery, chatbots, marketing templates and desktop agent tools. Both components run happily inside a VCL or FMX application, a service or a console process.

See what it can do →

Escape hatch

Proxies and Raw JSON

The Telegram component connects through HTTP, SOCKS5 and MTProto proxies, and when Telegram grows a call before the typed wrapper does, SendCustomRequest posts the raw TDLib JSON directly, so you are never waiting on a component update.

The Telegram surface →

Cross-platform

Five Targets for Telegram, Every Target for WhatsApp

TDLib ships native builds for Windows, macOS, Linux 64-bit, Android and iOS. The WhatsApp client is pure HTTPS, so it compiles wherever Delphi does. From Delphi 7 through RAD Studio 13 and on C++ Builder.

The feature matrix →

Reference pages for each component:

Telegram client WhatsApp client Feature matrix Pricing

THE CODE

Two Networks, the Same Shape

Create the component, set the credentials, hook the events, call the send methods. Both components live in the sgcLibs unit, and both read the same in Object Pascal and in C++ Builder.

uses
  sgcLibs;
var
  Telegram: TsgcTDLib_Telegram;
begin
  Telegram := TsgcTDLib_Telegram.Create(nil);
  Telegram.Telegram.API.ApiId   := '123456';
  Telegram.Telegram.API.ApiHash := 'your-api-hash';
  Telegram.Telegram.PhoneNumber := '+34600111222';

  Telegram.OnAuthenticationCode := TelegramAuthenticationCode;
  Telegram.OnMessageText        := TelegramMessageText;

  Telegram.Active := True;
end;

procedure TForm1.TelegramAuthenticationCode(Sender: TObject;
  var Code: string);
begin
  Code := InputBox('Telegram', 'Enter the code you received', '');
end;

procedure TForm1.TelegramMessageText(Sender: TObject;
  MessageText: TsgcTelegramMessageText);
begin
  Memo1.Lines.Add(MessageText.ChatId + ': ' + MessageText.Text);
  Telegram.SendTextMessage(MessageText.ChatId, 'received!');
end;

uses
  sgcLibs;
var
  WhatsApp: TsgcWhatsApp_Client;
begin
  WhatsApp := TsgcWhatsApp_Client.Create(nil);
  WhatsApp.WhatsAppOptions.PhoneNumberId := '123456789012345';
  WhatsApp.WhatsAppOptions.Token := 'EAAG...';

  WhatsApp.SendMessageText('+34666555444', 'hello from Delphi');

  WhatsApp.OnMessageReceived := WhatsAppMessageReceived;
  WhatsApp.StartServer;
end;

procedure TForm1.WhatsAppMessageReceived(Sender: TObject;
  const aMessage: TsgcWhatsApp_Receive_Message;
  var aMarkAsRead: Boolean);
begin
  Memo1.Lines.Add(aMessage.RawMessage);
  aMarkAsRead := True;
end;

The same shape in Object Pascal and in C++ Builder. The full feature matrix →

BEFORE YOU BUY

Two Things Worth Knowing First

What each component needs from you, and how the messages reach each network. Both answers are short, and both are on this page rather than in the small print.

Engines and transports

network      component             engine
Telegram     TsgcTDLib_Telegram    official TDLib (tdjson)
WhatsApp     TsgcWhatsApp_Client   HTTPS, Meta Graph API

credentials you bring
Telegram     api_id + api_hash (user), or a bot token
WhatsApp     PhoneNumberId + Token (Meta business account)

TDLib native builds: Windows, macOS, Linux 64-bit,
  Android and iOS. Point LibraryPath at the build
  for your platform.
The WhatsApp client is pure HTTPS: no native library,
  every platform Delphi targets.

sgcSocial is standalone

Standalone, the sgcWebSockets Core runtime is included: the HTTP and TLS layer, the JSON helpers and the webhook server the WhatsApp component hosts all ship in one installer, with full source code in the box.

Telegram ships with an engine

TsgcTDLib_Telegram loads the official TDLib library at runtime (tdjson.dll, libtdjson.so, libtdjson.dylib), the same engine the Telegram clients are built on. That is what makes a full user-account client possible: phone number sign-in with the 2FA password step, secret chats and the complete update stream, next to plain bot tokens. It also connects through HTTP, SOCKS5 and MTProto proxies.

WhatsApp needs only HTTPS

The WhatsApp Business Cloud API is hosted by Meta, so TsgcWhatsApp_Client is a pure HTTPS client plus a built-in webhook endpoint for inbound messages. There is no native library at all. You bring a Meta business account, a PhoneNumberId and a Token.

Delphi and C++ Builder

sgcSocial targets Delphi 7 through RAD Studio 13 and C++ Builder. The same two components also live inside sgcWebSockets, the Telegram client from the Standard edition up and the WhatsApp client from Professional up, so an existing sgcWebSockets license may already cover you. The free trial installer is the sgcWebSockets All-Access trial, so both components can be evaluated today.

TDLib HTTPS Built-in webhook HTTP · SOCKS5 · MTProto proxies Full source

Every component and property →

sgcSocial talks to the published surfaces of both networks: the TDLib JSON interface for Telegram and the Business Cloud API for WhatsApp. Messages, media, templates, keyboards, payments and webhooks are first-class methods and events, and full source code means nothing in between is a black box.

THE ECOSYSTEM

Ten Libraries, One Toolbox

sgcSocial is one of ten eSeGeCe component libraries for Delphi, C++ Builder and .NET. They share conventions, they ship with full source, and they deploy royalty-free.

sgcSocial

Telegram and WhatsApp Business client components for Delphi and C++ Builder. Standalone, with the sgcWebSockets Core runtime bundled in.

Learn more →

sgcWebSockets

WebSocket, HTTP/2, MQTT, AMQP, WebRTC, AI and 30+ API integrations for Delphi, C++ Builder, Lazarus and .NET. This is where the Core runtime lives.

Learn more →

sgcMQ

MQTT, AMQP 0.9.1 and 1.0, Apache Kafka and STOMP client components for Delphi and C++ Builder. Standalone, with the sgcWebSockets Core runtime bundled in.

Learn more →

sgcHTML

Server-side HTML and UI components on Bootstrap 5 and htmx. Put a live dashboard in front of the conversations sgcSocial handles.

Learn more →

sgcQUIC

Raw QUIC transport and an HTTP/3 client and server, with WebTransport. An add-on to sgcWebSockets Enterprise.

Learn more →

sgcAI

AI, LLM and MCP components for Delphi and C++ Builder. Seven LLM providers behind one component, plus MCP, embeddings and speech. Standalone, with the sgcWebSockets Core runtime bundled in.

Learn more →