Hi everyone, looking for an iOS Instagram DM protocol / messaging panel.
Requirements:
1. Send & receive Instagram DMs on iOS (ready-made preferred)
2. Works with existing session headers:
authorization, x-ig-device-id, x-ig-family-device-id, x-mid, user-agent
3. Ideally supports: inbox list, thread detail, send message, mark as read
Budget:
- Open to rental or one-time purchase
- Monthly per-account pricing or full buyout both OK
If you have a working product, please DM with:
- Feature list / API coverage
- Pricing (rent vs buy)
- Docs & support details
Thanks.
Hi everyone, I’d like to ask about the rate limits when scraping influencer follower lists using private Instagram Android APIs.
I’m using new accounts registered via the Android API (each assigned a dedicated US residential IP and used within three days of registration). I’ve tested both the REST endpoint (/api/v1/friendships/{id}/followers/) and the GraphQL FollowersList endpoint to fetch public follower lists; in both cases, the result is fixed at 25 items per page, and the count=200 parameter has no effect. A single account typically triggers a challenge_required response after scrolling through roughly 26 to 36 pages (about 700 followers). This happens regardless of speed—whether the interval is 12 seconds, 3 seconds, or 1.5 seconds per page—and some accounts get challenged as early as the 12th page.
Here are a few findings from my tests: accounts that get challenged remain challenged even after an IP change, indicating the restriction is tied to the account itself; however, using a fresh account to continue scrolling from the previous page's next_max_id cursor works fine, so the issue isn't the specific pagination point. There is also a delayed effect: accounts appear fine when checked on the day of scraping, but overnight, about 20% of them switch to challenge_required or login_required status.
I’d like to ask: when using new accounts to scrape follower lists, how many pages can you typically get through per account? Is hitting a challenge at this volume the standard limit for new accounts, or is there an issue with the request method (e.g., headers, device parameters) that could be optimized? Do older, "warmed-up" accounts have significantly higher limits? Thanks.