entinyGram · Plugins
Plugin documentation
Everything you need to write, build and publish a plugin for entinyGram and Inugram, from the first step to JVM-level hooks.
JavaScript and TypeScript
One .inu.js file running in an isolated QuickJS engine.
Permissions per call
Users see what a plugin asks for before they install it.
A catalog inside Telegram
Plugins ship in a channel and install from the app's Marketplace.
Getting started
Core concepts
The engineQuickJS, threads, lifecycle, errors, limits and the web globals.GrantsEvery permission, its scopes, tiers and how checks fail.UISettings pages, rows, icons, menus, actions and dialogs.Telegram APIAccounts, reading and sending, TL objects, raw RPC, events.InterceptionRewrite or drop RPCs, updates and outgoing messages.Network, files and storagefetch, blobs, the private directory, localStorage, timers.CanvasDraw images, stickers and video without leaving the plugin.
Low level
entinyGram SDK
Publishing
These pages explain the ideas and the reasons. For exact signatures read the typings in @inugram/plugin-types. Inugram plugins are experimental as a whole: APIs marked experimental may change.