find-api
Discover, document, and map all API endpoints of an Android application
v2026.7.31-4eb5d2f3 installs+3 in 7 days76 StarsMITsynced 12 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install theqmaks/find-apiWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package1c3f840f…3cb4a733
1c3f840f8572…ac643cb4a7331 file · 1.9 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/TheQmaks/areclaw/tree/main/.claude/skills/find-api@4eb5d2f
On this page
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.jsonFiles in this version
- SKILL.md3.8 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.7.31-4eb5d2f | Nov 13, 2026 | 4eb5d2f | 1c3f840f | Signed | – |
More from TheQmaks
All from this publisherMore in APIs, SaaS and identity
See the category- 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
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login