Yes. The protocol, the client API and the client source code are all open, and developers on any platform are welcome to use them. There are two separate routes in, and picking the right one saves a great deal of work.
Bot API
A simple HTTPS interface for building bots. You create the bot with @BotFather, receive a token, and call the endpoints from any language that can make an HTTP request. There is no protocol work and no cryptography to implement. Almost everything people want to build fits here.
Client API
The full MTProto interface used by the apps themselves, for building an actual Telegram client or anything that has to act as a user account rather than a bot. It needs an application identifier from my.telegram.org, and it is substantially more involved: authentication, session handling and encryption are yours to manage. TDLib exists to absorb most of that and is the sensible starting point.
Which one to choose
| If you want to | Use |
|---|---|
| Build a bot, an alert feed, a shop, a moderation tool | Bot API |
| Build a full client, or automate a user account | Client API, via TDLib |
| Embed a web app inside Telegram | Mini Apps, on top of the Bot API |
Where to start
The Getting Started section of core.telegram.org covers both routes. The bot documentation is complete enough to build from without reading anything else. If you are exploring what is possible first, the bot directory is a practical survey of what people have actually built.
Updated