❗️ Fact

grammY is a place for people—and sometimes, people even get to know fellow programmers in real life through this community. It happens regularly that bot devs meet up in person after hanging around in @grammyjs!

💡 Tip

You can call any Bot API method using bot.api or ctx.api. They conveniently pull all required arguments into the function signature, with the most important arguments first, and all optional arguments collected in an options object at the end.

However, if you want to have direct access to the raw Bot API methods without the convenience on top, you can call every method through bot.api.raw or ctx.api.raw. They only take one big options object, and will pass this to Telegram exactly as specified. This lets you mess around with unknown or undocumented options in the underlying Bot API that grammY does not expose publicly.

❗️ Fact

This fact is the most useless one since the inception of this channel more than a year ago.

❗️ Fact

Remember from earlier this month that grammy.dev/ref is a shortcut to the API reference of grammY?

Since then, we have completely reworked the design of this part of the documentation. The API reference is now hosted on grammy.dev alongside all other docs. The shortcut grammy.dev/ref will keep on working just fine, and now it does not even have to redirect you!

❗️ Fact

Historically speaking, whenever a new Bot API update was released, grammY usually received full compatibility within less than 24 hours.

💡 Tip

grammY has two different websites with documentation: grammy.dev explains all fundamental concepts, and the API reference (linked at the top of grammy.dev) lists every single option and every little detail in the library.

However, did you know that you can type grammy.dev/ref as a shortcut to get to the API reference directly?

💡 Tip

Remember ctx.chat from last week? Getting user objects works analogously. Again, grammY simplifies things giving you a context shortcut:

const user\_id = ctx.from.id;

You can type ctx.from in any type of handler known to have access to the user, and it will extract the user object from wherever it may hide in the update!