Summary of an article published on The Web Scraping Club on 2025-03-16 (free to read). Read the full article

Mobile apps often expose data that the website doesn’t. They can call different API endpoints, show information missing from the site, or exist with no website at all. Their JSON APIs also tend to have lighter protection than the web version. On one of our consulting jobs, an antibot that was a problem on the website was easy to get past through the app. Delivery apps are the obvious target.

The main obstacle is SSL pinning, where the app trusts only one specific certificate and refuses your proxy’s. We explain what pinning is, why developers use it and how to tell an app has it. Then we go through three setups: a rooted Android phone, a stock iPhone without jailbreak, and the jailbroken iOS case. For the hands-on part we use HTTP Toolkit and its manual iOS setup, intercepting a delivery app on a physical iPhone and reading the API calls it makes.

What’s inside

  • Why a pinned app fails the interception test, and which errors point to pinning rather than a bad proxy setup
  • Why Android and iOS differ in how they treat user-installed CA certificates
  • What to do with a pinned iOS app when you don’t want to jailbreak: switch to the Android version or use Frida and objection
  • Small iOS pitfalls: opening the certificate link in Safari, checking the setup with the HTTP Toolkit test page, and apps that demand an update

In the full article: Step-by-step HTTP Toolkit setup for iOS manual interception, screenshots of captured app requests, and links to the longer Frida pinning bypass tutorial.

Read the full article on The Web Scraping Club