API development tools
Register an application to receive the api_id and api_hash a client needs to connect.
Preview — this form does nothing
There is no backend behind it. The fields accept text so the layout can be reviewed; nothing is validated, submitted, saved or sent anywhere, and no credentials can be issued.
There is also nothing to connect to yet: GROM has no protocol layer for client applications. Why that matters before you plan around this page.
Register an application
What you would receive
After registering, this page shows the credentials. Example values, blurred the way the real page will treat a secret:
- App api_id
- 2040
- App api_hash
- b18441a1ff607e10a989891a5462e627
The api_id is not secret and identifies your app. The api_hash is, and it is shown once — behind a reveal, with a copy button — rather than left on screen.
Rules worth knowing before you register
- One application per account. Registering again shows the existing one rather than creating a second.
- Applications cannot be deleted — only edited. Title, URL, description and platform stay changeable; the short name does not.
- The pair is bound to your account. Abuse traced to it is traced to you, so it does not belong in an open-source repository or a client shipped to users who could extract it.
Planned beyond the basics
These are specified for the portal but are not part of the first version, and nothing here is committed to a date:
- Rotating the
api_hash, with the old value accepted for a short grace period so a rotation does not take your client down.
- Per-application usage: active sessions, daily call volume, error rate.
- An optional IP or CIDR allowlist.
- A notification to the account owner when the hash is used from somewhere new.