Feature Introduction

Convert Telegram sessions (usually .session files) and direct login accounts (Telegram client account information on Windows) into online code reception links.

Generated format as follows:

+12362081371|https://tgapiv2.miha.uk/Lyyer2zs85N8cykb/6d3a2bd7-2055-46f7-a321-f33b530f1891/GetHTML
+12362081372|https://tgapiv2.miha.uk/Lyyer2zs85N8cykb/6d3a2bd7-2055-46f7-a321-f33b530f1892/GetHTML
+12362081373|https://tgapiv2.miha.uk/Lyyer2zs85N8cykb/6d3a2bd7-2055-46f7-a321-f33b530f1893/GetHTML
+12362081374|https://tgapiv2.miha.uk/Lyyer2zs85N8cykb/6d3a2bd7-2055-46f7-a321-f33b530f1894/GetHTML

The first part is the Telegram account name (actually the phone number), and the second part is the verification code link. Clicking it will show content like this:

This way, after users enter their phone number, they can easily get the login content through the subsequent link. (Of course, if email registration is required, users will need to enter their email to complete the login).

Working Principle

Telegram itself is designed very nicely. It supports 32 devices online simultaneously - in technical terms, this is called "multi-point login technology".

Internally in the program, these devices are called sessions. In the Chinese Telegram community's colloquial technical terms, sessions are called "protocols". I won't comment further on this.

Since Telegram supports "multi-point login", to reduce its own costs, when a new device logs in, verification codes are prioritized to be sent to already logged-in devices. This design is very nice, reducing costs while greatly improving speed and reliability.

So, the principle of this tool is very clear:

• Active devices generated through program login - sessions are widely circulated and traded in the TG community.
• Put a session of an account on a reliable server, and when users log in to new devices with this account, get verification codes through the session on the server.
• Display the verification code to users on the webpage.

How to Use the Program

1. Rent or Independent Deployment

Well, there should be a shopping link here, but unfortunately it's not done yet 🤣🤣🤣🤣🤣

Please join the group: https://t.me/DeveloperTeamGroup and contact the group owner MiHa to purchase.

Pricing:

• Rental: 30u per month / 80u for 3 months [New users can apply for test accounts, first month can be paid monthly, subsequent renewals minimum 3 months]
• Independent Deployment: 500u one-time, includes one deployment. Includes 6 months technical support. (After expiration it's not a big deal, small issues will be fixed readily)

Let me explain:

Rental means using my server. Theoretically I could see the numbers you put on the server...

The thing is, the honest author has nearly 10k old accounts himself, generally not interested in yours...

Independent Deployment means you need to provide your own server and domain. Specifically, you can check this document: Click to visit

Generally account dealers with many numbers should consider independent deployment. Much lower risk. At least the author can't see your numbers.

2. Start Program and Configure

1. When the program opens, it looks like this:

   

2. Then, enter the rented customer information (Customer ID and password).

   

3. Save configuration.

   After saving configuration, it will prompt you to restart the program. To be safe, just restart. This is to prevent potential bugs, and has nothing to do with programmer laziness... 😂😂 [Actually it's just laziness, but this way is more reliable]

3. Import Session and Upload

There's not much to say about this. Note that when importing sessions, you don't select files but rather a directory containing sessions. This is more convenient.

After uploading, the server will assign a link to this number. This is the api or url mentioned in the document title. Don't ask why it's called this, it's just colloquial technical terms. 😂😂😂😂

4. Export API Links

This is the final product. Can be very very very conveniently sold using card issuing programs or card issuing bots. Speaking of which, dujiaoka is quite a good card issuing program. You can try it.

5. Customize Copyright and Contact Information

The new version actually added quite a few features. For example, it supports copyright information and tdata import. What's copyright? It's this thing:

You can fill it in at this position: (Below is a screenshot of the latest version - 2024/05/23)

Mainly some people insist on removing author information when they pay money.

6. Update

- 2024-07-26

Added the function of reversing the api back to local session after uploading. This prevents some forgetful people from accidentally deleting old sessions.

- 2024-10-03

This feature has been modified.

Mainly includes:

• Destroy the login device that has been imported (need to be uploaded first)
• Because some tenants have many numbers, they are now split into uploads and downloads.
• Support proxy selection.
• Support switching between old and new templates.

Below are explanations of new features in the new version:

1. Destroy to Prevent Recovery:

   • Essentially this deactivates the session (login device/multi-point login "point") already uploaded to the tgapi server.

   • Because recently account dealers haven't been very honest, recovering your accounts. So it's better to destroy after code reception.

   • Destruction requires a credential, contact MiHa to obtain. Don't worry, it's free... Just afraid you don't understand and click randomly. Once you really understand, it will be provided to you for free.

   • To prevent mistakes, accounts with only one device logged in are not allowed to be destroyed.

     

   • Destruction takes 5 seconds per account. Don't complain it's slow. You just want to destroy devices, not kill accounts. This rate is fast enough.

   • Destruction has prompts. Also needs to select simulation mode and proxy. This is like importing, try it yourself. Let's focus on not killing accounts.

2. Proxy Selection:

   • First need to be clear, this feature is provided for independent deployment customers. MiHa's server IPs are well-maintained quality IPs, don't need this feature.
   • This needs to get all available proxies. Click to get them. When exporting, you can select corresponding proxy.
   • Can be used by independent deployment customers with more niche numbers. If you're not confident about your IP, this feature isn't bad.

Note that getting server information and uploading to server both use pagination mode. Pay attention to the logs. If the logs don't indicate task completion, don't click anything. Wait for it to complete.

FAQ(Important)

• Can't open with double click

  This weird issue has happened before. Remember, you can't open this from the zip file, extract it first

  If can't open after extracting, it's probably due to xx Computer Manager, YY Computer Assistant.

  Use a virtual machine. Anyway this program basically has no performance overhead.

• Refresh server information, can't get content, freezes

  Check network. If you can't correctly access this site, then it's basically your network issue.

• Big error message

  Same as above. If confirmed not that, ask in group.

• Can I set link expiration time? How long maximum

  Set whatever you want. Control currently limits to 99. But estimated subsequent versions will limit to 3650

• What happens when link expires?

  Users can't receive codes anymore. That's all. Override regenerate to fix.

• What does maximum code reception times mean? Why limit

  Each code reception actually requires server to login account and search messages. To limit this number (because there's chance of account death), set an upper limit. Also prevents some newbies from using this service as code receiver.

  If unhappy just set it higher. Anyway my server performance is okay.

• Account died? Is it your program's fault?

  No...

  Upload part is done through decoding protocol files, won't cause any damage; code reception part has risks, but due to using very stable libraries, basically won't cause damage.

• Account died, buyer asks for refund what to do?

  Program has two types of errors. One called: Account dead. You don't need to refund buyer for this--because they successfully received codes. Another called Account temporarily has issues, contact seller. For this theoretically you should refund, they never successfully received codes, died on first login...

• What's password mean? Can you uniformly change passwords?

  Password is 2fa password. This platform completely doesn't need password to login and get verification codes. The only meaning of this password is to provide to code receiving customers, letting them see password for convenient login.

  This software has done everything possible to suppress account death rate. Doesn't do any account operations.

  Tool for uniformly modifying passwords: https://miha.uk/docs/tutor/telegram-format-convert/

• Why is link expiration time 0 days?

  0.99 days gets rounded to 0 days. That's all. -1 is expired.

• What does delete mean? Did you delete my local session? Server's?

  Delete means server delete. That's all. I don't do anything to imported local sessions. Just remember to backup yourself.

• Why no codes coming?

  First emphasize one point, no codes coming has completely completely nothing to do with this program. Unless you find this account actually gets codes, but my platform doesn't show them. Then come find me.

  Telegram control is strict, many garbage IPs, fake apps, accounts logged in multiple times in short term, etc just don't get codes. Suggest changing to ~3 month old official Telegram client + clean IP to login.

  Consider using this client: https://t.me/TGBotDevelopment/77

• Why doesn't it support tdata?

  tdata login puts relatively large pressure on server. Also has losses during conversion (yes, will kill accounts). Moreover, tdata itself is final sales use, what's point of converting it to api...

  Because of making money, now supports tdata. Really nice, using some black technology, doesn't need to consume too many resources now.

After-sales & Technical Support

Telegram: @MailSlot

Telegram Group: https://t.me/DeveloperTeamGroup