Why teams come to us
The situation is almost always the same: there is a platform your product needs to talk to, but there is no API documentation, no SDK, and no developer support from the vendor. The only thing that exists is the Android app — and it works perfectly.
That is enough. We decompile the APK, observe what happens when you log in, search, submit a form, upload a file, or trigger any other action. We rebuild those calls — including auth headers, session tokens, request signatures, and device values the app generates — as direct API calls your code can make without the app running at all.
What you get
Postman collection
Ready to import and run. Requests are grouped by action, not dumped in a flat list. Variables keep your credentials, tokens, and server addresses in one place. Login requests save the session values later requests need. Every request includes a working example.
Python client library
A clean Python class with one method per action. It handles login, token refresh, session management, error responses, and multi-step flows internally. Your code calls client.get_orders() instead of managing raw headers and cookies.
Both together
Use the Postman collection to inspect, test, and share individual calls with your team. Use the Python client to automate the same actions from your backend, data pipeline, or test suite.
What "without the app screen" actually means
Everything the user does by tapping through screens, your delivery does through code. No Android emulator. No Appium. No screen scraping. Direct API calls.
- The app logs in. Your client logs in — the same way, with the same tokens.
- The app searches. Your client runs the same search and returns the same results.
- The app submits a form. Your client posts the same data to the same endpoint.
- The app uploads a file. Your client uploads it with the same headers and signature.
- The app polls for a result. Your client polls and waits the same way.
- The app refreshes its token after an hour. Your client refreshes it automatically.
We handle the hard parts
Most apps do not just send a plain HTTP request. They create device IDs, sign requests with a timestamp and secret, maintain multi-step session state, check certificate pinning, and poll for async results. We rebuild all of it into the delivery.
- SSL pinning: Bypassed during analysis. The final client uses the correct certificate flow.
- Request signing: We rebuild the algorithm the app uses to sign each request — HMAC, timestamp-based, or custom.
- Device fingerprinting: Device IDs, app versions, platform values, and other generated fields are included.
- Token refresh: When access tokens expire, the client renews them the same way the app does.
- Multi-step actions: Actions that require two, three, or more requests are delivered as a single method call.
- WebSockets and polling: Live data subscriptions and background result checks are built into the Python client.
How the project runs
You send us the APK
Share the APK file or download link, a list of the actions you want to automate, and a test account. We review what you have and confirm the scope.
We map every action
We run the APK and walk through each agreed action. We capture the full request flow — not just the URLs, but the headers, timing, session values, and any pre-call setup the app performs.
We rebuild outside the app
We reconstruct the auth flow, token handling, request construction, and action sequence so they run without the APK or an Android environment.
We package and test the delivery
We build the Postman collection and Python client, run every agreed action through both, and compare results against the original APK. If they do not match, we fix it before you see it.
You receive the delivery
You get the Postman collection, Python client, setup instructions, usage examples, and the full test results. The source is yours to keep and modify.
What to send us
- The APK file or a direct download link.
- The list of actions you want to automate — search, submit, upload, check status, and so on.
- A test account with access to the actions on your list.
- Any sample files if an action involves uploading or attaching data.
- Your preference: Postman collection, Python client, or both.
No source code needed. No rooted device needed on your side. If you are not sure which actions to start with, tell us the use case and we will help you scope it.
Send us the APK and tell us what the app does.
Send us your APKAPK to API questions
Can you extract the API from an APK with no documentation?
Yes. We decompile the APK, intercept traffic for each action you need, and rebuild the full API call — including login, session tokens, headers, and request bodies — as a working Postman collection or Python client.
Can you handle APKs that use SSL pinning?
Yes. SSL pinning, request signing, device fingerprinting, and multi-step token refresh are all handled. The final delivery works without bypasses — we rebuild the proper flow the app uses.
What do I need to send you?
Send us the APK file or a download link, a list of the actions you need to automate, and a test account for apps that require a login. That is enough to scope the project.
Will the Postman collection work as a standalone tool?
Yes. It includes working requests, login steps, environment variables, session handling, correct headers, and a saved example for every covered action. You can run any action without touching the app.
What does the Python client do exactly?
It exposes one clear method for each API action. It handles login, token refresh, session state, request construction, and error handling internally. Your code calls client.search_orders() — not raw HTTP.
Can you cover the entire app or just specific actions?
Both. We can scope a short list of critical actions or cover the full app. We recommend starting with the actions that block you first, then expanding from there.
How do you verify the delivery works?
We run the same action in the original APK and in your Postman collection or Python client. Both must produce the same result. We fix any difference before handover.
Can this work with apps that use WebSockets or background polling?
Yes. We handle WebSocket connections, server-sent events, long polling, and background jobs that apps use to push or receive live data.
Do I need root access or a jailbroken device?
We handle the analysis environment on our side. You only need to send us the APK and a test account. No rooted device is required from you.
What if the app updates and breaks the client?
If the app changes an API endpoint or authentication method, the client may need updating. We can scope a maintenance arrangement, or we can rework specific actions if the app changes significantly.