<?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: Sinister</title>
    <description>The latest articles on DEV Community by Sinister (@sinister2000).</description>
    <link>https://dev.to/sinister2000</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3864224%2Ff554357d-d906-4055-b0e7-c758f360e9b8.png</url>
      <title>DEV Community: Sinister</title>
      <link>https://dev.to/sinister2000</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sinister2000"/>
    <language>en</language>
    <item>
      <title>Stop scraping websites manually. I built APIs for football and anime data.</title>
      <dc:creator>Sinister</dc:creator>
      <pubDate>Mon, 06 Apr 2026 17:01:26 +0000</pubDate>
      <link>https://dev.to/sinister2000/stop-scraping-websites-manually-i-built-apis-for-football-and-anime-data-id4</link>
      <guid>https://dev.to/sinister2000/stop-scraping-websites-manually-i-built-apis-for-football-and-anime-data-id4</guid>
      <description>&lt;h1&gt;
  
  
  Stop scraping websites manually. I built APIs for football and anime data
&lt;/h1&gt;

&lt;p&gt;If you have ever tried scraping websites for data, you already know how painful it gets.&lt;/p&gt;

&lt;p&gt;Selectors break. HTML changes. Your app stops working for no clear reason.&lt;/p&gt;

&lt;p&gt;I ran into this problem while building projects that needed football news and anime data. Instead of constantly fixing scraping scripts, I decided to build a simple solution.&lt;/p&gt;

&lt;p&gt;I created two APIs that return clean structured data so you do not have to deal with parsing HTML.&lt;br&gt;
You will get all the info from my landing pages :)&lt;/p&gt;

&lt;h2&gt;
  
  
  APIs
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Football API
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Landing page&lt;/strong&gt; &lt;br&gt;
&lt;a href="https://football-scraper.netlify.app/" rel="noopener noreferrer"&gt;https://football-scraper.netlify.app/&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Anime API
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Landing page&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
&lt;a href="https://anime-scraper.netlify.app/" rel="noopener noreferrer"&gt;https://anime-scraper.netlify.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;RapidAPI&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
&lt;a href="https://rapidapi.com/arkasarkar2000/api/aniscraper" rel="noopener noreferrer"&gt;https://rapidapi.com/arkasarkar2000/api/aniscraper&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What these APIs solve
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;No need to write scraping logic&lt;/li&gt;
&lt;li&gt;No broken selectors when websites change&lt;/li&gt;
&lt;li&gt;Clean JSON responses ready to use&lt;/li&gt;
&lt;li&gt;Faster development for side projects and apps&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Current progress
&lt;/h2&gt;

&lt;p&gt;The football API is already at around 1K API calls with a few paying users. That gave me confidence to build and launch the anime API as well.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who this is for
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Developers building apps or side projects&lt;/li&gt;
&lt;li&gt;Anyone who needs quick access to structured data&lt;/li&gt;
&lt;li&gt;People tired of maintaining scrapers&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you are building something in this space, I would love to hear your feedback.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>api</category>
      <category>javascript</category>
      <category>node</category>
    </item>
  </channel>
</rss>
