-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to get an API ID #6
Comments
We have an idea that people might figure that by themself to understand basics of MTProto and Telegram Api |
There is some merit to that thought but, that also defeats the purpose of a I do think you need to do something to filter out superfluous request for
|
Anyway the method "register.saveDeveloperInfo" it is not implemented in the library. I tried to do my own implementation: import java.io.IOException; import org.telegram.tl.StreamingUtils;
*/ public class TLSaveDeveloperInfo extends TLMethod {
;
} |
I appreciate that very much! -//---------// On Fri, Feb 28, 2014 at 12:27 AM, dmasoft notifications@github.com wrote:
|
I'm trying to develop the code for getting an API_ID but I've suddenly started to get connection time outs from 95.142.192.65:80. |
There server still appears to be offline: http://95.142.192.65... |
You can try with 173.240.5.253:443 |
Yes, there are mistake in documents, there are old test server ip. You may use 173.240.5.253:443 |
With the new IP Address I get a BooleanTrue repsonse but no SMS message Parameters 173.240.5.253:443: OakhurstTelegramApi#1001:Phase 0 in 2 ms |
dmasoft I have used your class but when I do the RPC call am getting an TelegramApi#1001:mtproto#1001| RPC #2: Error #400 INPUT_FETCH_ERROR Can anyone help me with this? |
I'm getting a TimeOutException after "Authorizer:Solved PQ in ... ms" with server 109.239.131.195:80 and with server 173.240.5.253:443 |
Hi! Why was this issue closed? I don't think a solution was reached here. I am currently having troubles getting an API_ID, and am hoping for an update to this thread. Thanks! |
@brain56 , you can get API_ID at https://my.telegram.org/myapp Telegram will send the password to your telegram messenger |
@saturngod, thanks! :D |
I'm currently using the API ID and Hash specified in the Telegram-S project with some very basic calls. I'm sure you don't want me doing that long-term.
Reading the documentation at https://core.telegram.org/api/obtaining_api_id only helps at a conceptual level. Is there a quick solution for registering for an API ID? Possibly a Java implementation? Or can you do it for me?
What ever it takes to help us move forward.
The text was updated successfully, but these errors were encountered: