Ruby on Rails开发者求助：如何提取Instagram用户公开联系邮箱？

Hey fellow RoR dev! Let's tackle this Instagram public contact email extraction for your MVP—since the web UI doesn't expose that contact info, the private API route is definitely your best bet over Appium, so let's dive into that first.

Instagram's public Graph API doesn't return public contact emails, but the official mobile app uses private API endpoints that do expose this data. Here's how to implement this in Rails:

• Authenticate like the mobile app: You'll need to mimic the app's login flow to get authenticated cookies. You can use the unofficial instagram_private_api gem to handle this, or manually send a POST request to Instagram's login endpoint with your credentials (use a tool like Charles Proxy to intercept the app's login traffic to get the exact endpoint and headers).
• Fetch user profile info: Once authenticated, the endpoint you need is https://i.instagram.com/api/v1/users/{user_id}/info/. This returns a JSON object containing public_email if the user has set it.
• Rails-specific code example:

  require 'httparty'
  
  def fetch_instagram_contact_email(username)
    # First, convert username to user ID
    user_id = get_user_id(username)
  
    # Use headers copied from the official app's network requests
    headers = {
      "User-Agent" => "Instagram 292.0.0.10.108 Android",
      "X-IG-App-ID" => "936619743392459",
      "Cookie" => "your_authenticated_session_cookie" # Get this via login flow
    }
  
    response = HTTParty.get("https://i.instagram.com/api/v1/users/#{user_id}/info/", headers: headers)
    user_data = JSON.parse(response.body)
  
    user_data.dig("user", "public_email") || "No public contact email available"
  end
  
  def get_user_id(username)
    # Endpoint to resolve username to user ID (no auth needed for this one)
    response = HTTParty.get(
      "https://i.instagram.com/api/v1/users/web_profile_info/?username=#{username}",
      headers: {"X-IG-App-ID" => "936619743392459"}
    )
    JSON.parse(response.body).dig("data", "user", "id")
  end
  

• Caveats: Using private APIs violates Instagram's Terms of Service, so keep this in mind if you plan to scale. For a single-account MVP, though, this should work reliably without hitting major rate limits.

If the API route stops working, here's a streamlined way to set up Appium for your single-account use case (no need for a full emulator farm):

• Use a real Android device with USB debugging enabled instead of an emulator—it's faster and more stable.
• Integrate the appium_lib gem into your Rails app. Here's a quick snippet to extract the email:

  require 'appium_lib'
  
  caps = {
    platformName: 'Android',
    deviceName: 'Your Connected Device',
    appPackage: 'com.instagram.android',
    appActivity: 'com.instagram.mainactivity.MainActivity'
  }
  
  driver = Appium::Driver.new(caps, true).start_driver
  driver.wait_true(10) { driver.find_element(:accessibility_id, "Search and Explore") }
  
  # Navigate to target user's profile
  driver.find_element(:accessibility_id, "Search and Explore").click
  driver.find_element(:id, "com.instagram.android:id/action_bar_search_edit_text").send_keys("target_username")
  driver.find_element(:xpath, "//android.widget.TextView[@text='target_username']").click
  
  # Tap contact button and extract email
  driver.find_element(:id, "com.instagram.android:id/profile_action_button").click
  email = driver.find_element(:id, "com.instagram.android:id/contact_option_email").text
  
  puts email
  driver.quit
  

• Downsides: This is slower, prone to breakage if Instagram updates their UI, and requires physical device setup—save this for when the API route fails.

• Start with the private API approach first—it's faster and easier to maintain for a single-account use case.
• Test with users you know have public contact emails to validate your implementation.
• Add error handling for cases where the user has no public email, or the API request fails.

内容的提问来源于stack exchange，提问作者Ernani Rocha