Quick answer: Stage + exact error + time + submission state is more useful than saying it does not work. Support uses these facts to identify next steps. Keep verification codes, two-step passwords and API Hash out of chat.
For help, contact support at gettgapi.com/en/help#contact. Already have an access code? Start at gettgapi.com/en/redeem.
Contact human support
Open gettgapi.com, select Contact support at the lower right and enter the website bot. Send /start, then describe the issue in the same chat. Support replies there.
You do not need to send the problem to multiple bots. Keep one conversation and update it if the state changes.
Four facts for the first message
- Stage: phone submission, waiting for a code, code entry, app creation or configuring software after receiving results.
- Exact wording: for example
ERRORorToo many tries. Do not substitute a guessed cause. - Time and environment: approximate time and timezone, phone or computer, browser and any window switches.
- Submission state: whether Create was clicked, whether ID and Hash appeared, and whether GetTGAPI has an active record.
No packet capture or complete log upload is needed. A web ERROR differs from software API_ID_INVALID or FLOOD_WAIT. Official error meanings
Copyable template
This is a blank template, not a customer case. Fill it truthfully and write Not sure where needed.
I need help with a TG API application.
Location: official portal / GetTGAPI / other software
Current step: phone / code / Create application / checking result
Exact message:
Time and timezone:
Device and browser:
Did I click Create? Yes / No / Not sure
Have I seen complete ID and Hash? Yes / No
What I have tried:
Is the original application page still open? Yes / No
If it says only ERROR, report only ERROR. Do not invent a technical error number.
Screenshots: keep context, hide secrets
Keep the step name, alert and field guidance. An image showing only ERROR usually cannot identify the stage.
Mask full phone numbers, verification codes, two-step passwords, complete access codes, ID and Hash where unnecessary. To investigate a code problem, first explain the need in the designated support chat, then provide only the requested information. Do not post it in public groups or article comments.
Never forward complete Telegram verification messages, cookies, session files or credential-bearing URLs. Deleting a leaked chat image does not retract copies another device may have saved.
Should I keep clicking while waiting?
If Create was submitted or a result is being checked, keep the original record. Do not submit again for a fresh screenshot: it complicates investigation without proving the old request failed.
For an unsubmitted format problem, correct the field as directed. Stop when frequency limits appear. ERROR alone gives no universal waiting time.
Continue after review
Support explains the appropriate next step. With a valid code, use gettgapi.com/en/redeem. For existing apps or pending records, follow the corresponding checks before buying again.
See the complete assistance flow. Human help advances the actual issue; it does not promise to lift account restrictions or reply within a fixed time.