<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Saraswat Bhowmik</title>
    <description>The latest articles on DEV Community by Saraswat Bhowmik (@saraswat_bhowmik_638f7521).</description>
    <link>https://dev.to/saraswat_bhowmik_638f7521</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4257572%2Fa1504df5-94c4-486c-bc4a-4f2d514966a1.jpg</url>
      <title>DEV Community: Saraswat Bhowmik</title>
      <link>https://dev.to/saraswat_bhowmik_638f7521</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/saraswat_bhowmik_638f7521"/>
    <language>en</language>
    <item>
      <title>hikerapi</title>
      <dc:creator>Saraswat Bhowmik</dc:creator>
      <pubDate>Sat, 21 Nov 2026 15:38:12 +0000</pubDate>
      <link>https://dev.to/saraswat_bhowmik_638f7521/hikerapi-4j1o</link>
      <guid>https://dev.to/saraswat_bhowmik_638f7521/hikerapi-4j1o</guid>
      <description>&lt;p&gt;Last month, my hashtag tracking script finally died. I had been running a headless browser setup to check public profiles in my niche and see which tags correlated with higher engagement, and Instagram’s login walls and rate-limit blocks brought the whole pipeline to a halt. Spending weekends rotating proxies and fixing broken selectors wasn't helping me analyze content performance.&lt;/p&gt;

&lt;p&gt;I needed a reliable way to pull profile metrics and post metadata without maintaining fragile scraping infrastructure, so I switched to a REST API approach using HikerAPI.&lt;/p&gt;

&lt;p&gt;Why an API Beats Custom Scraping&lt;br&gt;
Using a dedicated REST endpoint eliminates the constant maintenance of headless browsers, proxy rotation, and DOM changes—you just send a standard HTTP request and get structured JSON back.&lt;/p&gt;

&lt;p&gt;Pulling Profile Data in Python&lt;br&gt;
To figure out which hashtags are actually working in a given niche, the first step is pulling baseline profile data (like follower counts and media totals) for accounts in that space so you can normalize their engagement rates.&lt;/p&gt;

&lt;p&gt;You only need the standard requests library to get started. First, install it if you haven't already:&lt;/p&gt;

&lt;p&gt;Bash&lt;br&gt;
pip install requests&lt;br&gt;
Next, grab your API key from HikerAPI (they include 100 free requests to test things out, and pricing starts at $0.001 per request after that).&lt;/p&gt;

&lt;p&gt;Here is the exact snippet to fetch a user's profile object by their username:&lt;/p&gt;

&lt;p&gt;Python&lt;br&gt;
import requests&lt;/p&gt;

&lt;p&gt;headers = {"x-access-key": "YOUR_KEY"}&lt;br&gt;
r = requests.get(&lt;br&gt;
    "&lt;a href="https://api.hikerapi.com/v2/user/by/username" rel="noopener noreferrer"&gt;https://api.hikerapi.com/v2/user/by/username&lt;/a&gt;",&lt;br&gt;
    params={"username": "spotify"},&lt;br&gt;
    headers=headers,&lt;br&gt;
)&lt;br&gt;
print(r.json())&lt;br&gt;
Replace "YOUR_KEY" with your actual access key and swap "spotify" for any public handle in your niche.&lt;/p&gt;

&lt;p&gt;How I Use This for Hashtag Analysis&lt;br&gt;
Once the JSON response comes back, I extract the user's pk (user ID) and follower_count. From there, I pass that ID into the media endpoints to pull recent posts, extract the hashtag arrays from the captions, and calculate engagement relative to their follower size.&lt;/p&gt;

&lt;p&gt;Instead of guessing which tags are saturated or dead, I can quickly cross-reference which specific hashtags appear on posts that outperform an account's baseline reach—all in a lightweight Python script that actually stays online.&lt;/p&gt;

</description>
      <category>api</category>
      <category>automation</category>
      <category>webscraping</category>
    </item>
    <item>
      <title>Tracking Which Instagram Hashtags Actually Drive Reach Using Python
Last month, my hashtag tracking script finally died. I had been running a headless browser setup to check public profiles in my niche and see which tags correlated with higher engagement,</title>
      <dc:creator>Saraswat Bhowmik</dc:creator>
      <pubDate>Sat, 21 Nov 2026 15:36:33 +0000</pubDate>
      <link>https://dev.to/saraswat_bhowmik_638f7521/tracking-which-instagram-hashtags-actually-drive-reach-using-python-last-month-my-hashtag-4kdb</link>
      <guid>https://dev.to/saraswat_bhowmik_638f7521/tracking-which-instagram-hashtags-actually-drive-reach-using-python-last-month-my-hashtag-4kdb</guid>
      <description></description>
      <category>automation</category>
      <category>python</category>
      <category>socialmedia</category>
      <category>webscraping</category>
    </item>
  </channel>
</rss>
