Quick answer: Identify whether the failure happened while sending a code, verifying, creating an app or configuring software. GetTGAPI offers support that starts from the current record; not every ERROR calls for a new application.
For help, contact support at gettgapi.com/en/help#contact. Already have an access code? Start at gettgapi.com/en/redeem.
Keep the current record
After a timeout or error, do not immediately switch browsers and start again. Check whether the existing application record remains, its status, and whether a result has appeared.
Share non-secret error text and an approximate time with support. Never send verification codes, two-step passwords, complete API Hash or full URLs containing authorization data.
Locate the ERROR stage
For an unexplained ERROR, read 10 situations explained:
- Immediately after submitting a number: number and account state.
- After entering a received code: wrong or expired code.
- After app details: App title and Short name.
- Spinner, error or timeout after Create: check for success first.
- Returned to the number form after verification: portal session and navigation.
- Suspected account-age or phone limits: new and old accounts, mobile versus desktop.
The same short message can occur at different stages. Without an explanation, it does not establish an account ban, an IP problem or an unavailable short name.
Other common issues
| Issue | Guide |
|---|---|
| No portal code | Number, account and status checks |
| Too many tries / too many requests | Stop repeated attempts and wait |
| Portal timeout, blank page or connection failure | Browser and portal access |
| Existing application or lost credentials | Find the existing ID and Hash |
| Copy failed or record missing after deletion | Saving and deletion scope |
| API_ID_INVALID in software | Configuration checks |
| FLOOD_WAIT in software | Request limits and published API IDs |
Client authorization errors such as SESSION_PASSWORD_NEEDED do not directly describe the developer portal flow. Our application service does not request two-step passwords. Official client authorization
Input or app details are wrong
Include the correct country code, preserve verification-code case, and follow app-title and short-name requirements. Correct the field actually identified by the page. Do not put phone numbers or passwords into app names. Before starting a new request, check whether the old one is still running.
A timeout with an unknown outcome
A timeout means the response did not fully arrive; it does not prove the app was never created. Read the app page to check for a result before submitting Create again.
GetTGAPI temporarily retains necessary context and reserves a use while checking uncertain outcomes. Keep your current browser session. Contact support if the page requests manual review.
An existing app is reported
Usually the right action is to read its credentials, not create another set. See existing API credentials. We retrieve an existing app and do not promise a second set. Usage treatment depends on the current record and verified outcome, not just whether a button click appeared successful.
Why available uses decrease temporarily
Starting reserves one use; a verified success consumes it. Confirmed failure or safe cancellation releases it. Unknown outcomes must be checked before releasing a reservation.
This does not mean each click or refresh consumes another use. Judge balances against application records and outcomes. See service terms.
When to ask for help
Contact support if the page requests manual review, progress does not change for an extended period, or the verified result and balance disagree. Describe the current status and time.
Support replies in the same bot chat. Upstream and network conditions vary; fixed completion times and universal success are not promised. When a result appears, copy and save it promptly.