onnet / erl-tdlib

Erlang bindings to tdlib/td written in Rust

tdlib

Erlang library interfacing with tdlib, a telegram client library created by Telegram.

Build

Have libtdjson.so from tdlib installed in your library path.

Have Rust installed.

Have rebar3 installed.

Clone, cd to repository and compile:

$ rebar3 get-deps
$ rebar3 compile

Getting started

Fetch app_id and app_hash at https://my.telegram.org/apps

In this example we will use following placeholders:

• app_id : 34567
• app_hash : qwertyasdfgh123456qweytr
• telegram account phone number: [phone]
• database directory (will be created by tdlib when needed) : tdlib_db
• code Telegram sends you after sending them phone number : 23456
• password : pAssWorD..1

Example session:

$ rebar3 shell

1> {ok, Pid} = tdlib:start_link().
2> tdlib:config(Pid, [{api_id, <<"34567">>}, {api_hash, <<"qwertyasdfgh123456qweytr">>}, {database_directory, <<"tdlib_db">>}]).
3> tdlib:phone_number(Pid, <<"[phone]">>).
4> tdlib:auth_code(Pid, <<"23456">>).
5> tdlib:auth_password(Pid, <<"pAssWorD..1">>).

When authenticated, next run with same db directory will authenticate automatically, you don't need to enter phone, code or password.

Another example, with registering tdlib server (any valid ServerName from gen_server:start_link/4 specification will do: {local, Atom}, {global, Atom} or {via, Module, Term}). Here we suppose tdlib_db directory is already initialized with authenticated account

$ rebar3 shell

1> {ok, Pid} = tdlib:start_link({local, session1}, [{api_id, <<"34567">>}, {api_hash, <<"qwertyasdfgh123456qweytr">>}, {database_directory, <<"tdlib_db">>}]).
2> whereis(session1).
<0.186.0>

Interface

See edoc documentation

Building docs

$ rebar3 edoc