find-api
Discover, document, and map all API endpoints of an Android application
v2026.7.31-4eb5d2f3 installazioni+3 in 7 giorni76 StelleMITsincronizzato 12 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install theqmaks/find-apiScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto1c3f840f…3cb4a733
1c3f840f8572…ac643cb4a7331 file · 1.9 KBScansioneBasso1 segnalazione
- Link a domini esterni
Sorgentegithub.com/TheQmaks/areclaw/tree/main/.claude/skills/find-api@4eb5d2f
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
You are mapping the complete API surface of an Android application. Goal: a developer could rebuild the API client from your output.
Input
$ARGUMENTS— package name or APK path
Phase 1: Static Discovery
1a. Decompile (if not already done)
jadx -d workspace/output/$PKG --deobf $APK1b. Quick Automated Scan
# apkleaks finds URLs, endpoints, API keys in seconds
apkleaks -f $APK --json -o workspace/reports/$PKG-endpoints.jsonReview output — often catches endpoints that manual grep misses (string concatenation, BuildConfig fields).
1c. Retrofit Interfaces
Search for annotated interfaces — this is the goldmine:
grep -rn "@GET\|@POST\|@PUT\|@DELETE\|@PATCH\|@HEAD\|@HTTP" workspace/output/$PKG/For each interface found:
- Map method → HTTP verb + path
- Map
@Query,@Field,@Body,@Pathparameters - Map return type (usually
Call<Model>orObservable<Model>) - Find the model classes for request/response
1c. Base URL Discovery
grep -rn 'baseUrl\|BASE_URL\|API_URL\|SERVER_URL\|ENDPOINT\|api_host' workspace/output/$PKG/
grep -rn 'https\?://[a-zA-Z0-9.-]*api[a-zA-Z0-9.-]*' workspace/output/$PKG/1d. Non-Retrofit HTTP
Look for direct HTTP usage:
grep -rn 'HttpURLConnection\|OkHttpClient\|Volley\|WebView.*loadUrl' workspace/output/$PKG/1e. WebSocket / Real-time
grep -rn 'WebSocket\|ws://\|wss://\|Socket\.IO\|firebase' workspace/output/$PKG/1f. GraphQL / gRPC
grep -rn 'graphql\|/graphql\|query.*{.*}\|ManagedChannel\|\.grpc\.' workspace/output/$PKG/Phase 2: Handle Obfuscation
If endpoint strings are obfuscated:
- Look for string constants with URL patterns (
/api/,/v1/,/v2/) - Look for JSON field names (they reveal data models)
- Check
strings.xmland other resource files for URLs - Check
res/raw/andassets/for config files
Phase 3: Dynamic Discovery (if device available)
If static analysis is insufficient or obfuscated:
# Option A: Frida API tracer (captures Retrofit calls)
frida -U -f $PKG -l workspace/frida-scripts/api-tracer.js
# Option B: Full HTTP logging (captures all traffic)
frida -U -f $PKG -l workspace/frida-scripts/ssl-bypass.js -l workspace/frida-scripts/http-logger.js
# Navigate the app to trigger API calls
python pytools/ui_explorer.py snapshot
# Walk through key screensSave traffic to workspace/traffic/$PKG-traffic.json
Phase 4: Correlation
Build the complete picture:
- UI Screen → Activity → API Call: Which screen triggers which endpoint?
- Auth Flow: Login endpoint → token → how token is passed → refresh flow
- Data Models: Request/response JSON structures
Phase 5: Output
API Documentation (Markdown)
Save to workspace/reports/$PKG-api.md:
# API Documentation: <App Name>
## Base URLs
- Production: https://api.example.com
- CDN: https://cdn.example.com
## Authentication
- Type: Bearer JWT / API Key / OAuth2
- Login: POST /auth/login → { access_token, refresh_token }
- Token passed via: Authorization header / cookie / custom header
## Endpoints
### Auth
| Method | Path | Auth | Body | Response |
|--------|------|------|------|----------|
| POST | /auth/login | No | { email, password } | { token, user } |
| POST | /auth/refresh | Bearer | { refresh_token } | { token } |
### Users
| Method | Path | Auth | Params | Response |
...Postman Collection
If traffic was captured:
python pytools/traffic_to_collection.py frida workspace/traffic/$PKG-traffic.json --name "$PKG API" --output workspace/collections/$PKG.jsonFile di questa versione
- SKILL.md3.8 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.7.31-4eb5d2f | 13 nov 2026 | 4eb5d2f | 1c3f840f | Firmata | – |
Altro da TheQmaks
Tutto da questo editoreAltro in API, SaaS e identità
Vai alla categoria- testing-for-sensitive-data-exposuremukul975/testing-for-sensitive-data-exposure5
- performing-jwt-none-algorithm-attackmukul975/performing-jwt-none-algorithm-attack5
- sharp-edgestrailofbits/sharp-edges4
- hydraaeondave/hydra4
- implementing-google-workspace-admin-securitymukul975/implementing-google-workspace-admin-security4
- implementing-api-security-posture-managementmukul975/implementing-api-security-posture-management4
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login