Android app: how to connect it
The existing Android app works with this API without changes. This page summarises how it connects and what to expect.
How it connects
- The app base address:
https://seo.gtechgroup.it/api/(unchanged from the old site). The app appends theseo/...paths to it. - Sign-in: the app sends
POST /api/loginwith email and password and receives{"data":{"api_key":"...","user":{...}}}. The key is stored and used asAuthorization: Bearer. - Keys already issued by the old site keep working: there is no need to sign in again.
- The app file can be downloaded from https://seo.gtechgroup.it/gtgseo-app-v21-0.14.4.apk.
curl -X POST https://seo.gtechgroup.it/api/login \
-H 'Content-Type: application/json' \
-d '{"email":"nome@esempio.it","password":"********"}'
What works
All the paths the app calls are present (taken from analysing the app):
| POST | /api/login |
| GET | /api/seo/status |
| GET | /api/seo/projects |
| GET | /api/seo/projects/{id} |
| POST | /api/seo/projects/{id}/keywords |
| POST | /api/seo/projects/{id}/refresh |
| GET | /api/seo/keywords/{id}/history |
| GET | /api/seo/spider |
| GET | /api/seo/spider/{id}/pages |
| GET | /api/seo/geo |
| GET | /api/seo/ai-visibility |
| GET | /api/seo/ai-engine |
| GET | /api/seo/ai-competitor |
| GET | /api/seo/prompt-research |
| POST | /api/seo/keyword-research |
| GET | /api/seo/alerts |
| PATCH | /api/seo/alerts/{id} |
| GET | /api/seo/search-console |
| GET | /api/seo/search-console/sites |
| GET | /api/seo/analytics |
| GET | /api/seo/analytics/properties |
| POST | /api/seo/device-tokens |
| DELETE | /api/seo/device-tokens/{token} |
Search Console and Analytics answer with the data of the connected Google account; without a connection they answer 409 and the app shows a message.
Differences to know
- Login returns a new key on every sign-in (before, it was a fixed user key). The app stores it as before, so nothing changes for the user.
- If the account has 2FA enabled, login answers 401 with
code: twofa_requireduntil the code (twofa_token) is sent. If the app version has no such field, use an API key created from the account. - Project statistics (
stats) have the full shape:tracked,ranking,avg_position,buckets,gained,lost,timeline. - Push notifications need the messaging service key on the server: until it is configured, device registration works but no notifications arrive.
Verification: compatibility was checked against the app code and with automated tests, not yet with the app installed on a real device.
