loading...

FeediRSS API

daviducolo profile image Davide Santangelo Updated on ・5 min read

I just implemented an service that allow to transform RSS feed into REST API. Take a look at

GitHub logo davidesantangelo / feedirss-api

RSS as RESTful. This service allows you to transform RSS feed into an awesome API.

License contributions welcome Open Source Helpers

FeediRSS

The best RESTful RSS experience you can find.

FeediRSS turns feed data into an awesome API. The API simplifies how you handle RSS, Atom, or JSON feeds. You can add and keep track of your favourite feed data with a simple, fast and clean REST API. All entries are enriched by Machine Learning and Semantic engines.

Search Engine

Take a look at a little search engine developed in React around this API.

www.datorss.com

Feedback is welcome on its repository.

Example

curl 'https://api.feedirss.com/search/entries?q=news' | json_pp
{
  "data": [
    {
      "id": "86b0f829-e300-4eef-82e1-82f34d03aff6"
      "type": "entry"
      "attributes": {
        "title": "\"Pandemic, Infodemic\": 2 Cartoon Characters Battling Fake News In Assam"
        "url": "https://www.ndtv.com/india-news/coronavirus-pandemic-infodemic-2-cartoon-characters-battling-fake-news-in-assam-2222333",
        "published_at": 1588448805,
        "
Enter fullscreen mode Exit fullscreen mode

   RestClient.get "https://api.feedirss.com/feeds", { Authorization: "Token <TOKEN>" }
Enter fullscreen mode Exit fullscreen mode
   RestClient.get "https://api.feedirss.com/search/entries?q=dev.to", { Authorization: "Token <TOKEN>" }
Enter fullscreen mode Exit fullscreen mode
{
  "data": [
    {
      "id": "fe8cbc4d-fe19-48c0-9017-283ea9a12cca",
      "type": "entry",
      "attributes": {
        "title": "Thoughts on migrating to TypeScript and improving the overall quality of the frontend DEV codebase",
        "url": "https://dev.to/ben/thoughts-on-migrating-to-typescript-and-improving-the-overall-quality-of-the-frontend-dev-codebase-1121",
        "published_at": 1555524852,
        "body": "\n\n<p>I think the evolution and increased popularity of TypeScript over the past year or so means that it is a good time to migrate towards using it on DEV.</p>\n\n<p>Nick Taylor has been the biggest proponent, but it all jives with my view of things.</p>\n\n<p>Read more here:</p>\n\n\n<div class=\"ltag__link\">\n        <a href=\"/nickytonline\" class=\"ltag__link__link\">\n          <div class=\"ltag__link__pic\">\n            <img src=\"https://res.cloudinary.com/practicaldev/image/fetch/s--wsDCLFo5--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://res.cloudinary.com/practicaldev/image/fetch/s--HhqKWFvW--/c_fill%2Cf_auto%2Cfl_progressive%2Ch_150%2Cq_auto%2Cw_150/https://thepracticaldev.s3.amazonaws.com/uploads/user/profile_image/9597/d1d224a1-9ad1-4bd4-90c3-57f88c6c9bf5.jpeg\" alt=\"nickytonline image\">\n          </div></a>\n          <a href=\"/nickytonline/dev-to-with-a-typescript-or-flow-frontend-codebase-1n33\" class=\"ltag__link__link\">\n            <div class=\"ltag__link__content\">\n              <h2>dev.to with a TypeScript or Flow frontend codebase?</h2>\n              <h3>Nick Taylor</h3>\n              <div class=\"ltag__link__taglist\">\n<span class=\"ltag__link__tag\">#meta</span><span class=\"ltag__link__tag\">#javascript</span><span class=\"ltag__link__tag\">#typescript</span><span class=\"ltag__link__tag\">#flow</span>\n</div>\n            </div>\n        </a>\n      </div>\n\n\n<p>I did not want us to be too far on the bleeding edge of frontend technology and that continues to be my stance, but I think TypeScript is in a good place and Rails' support of \"modern\" JavaScript is likewise in a good place.</p>\n\n<p>As it currently stands, we have some of our JavaScript in the \"old\" <code>app/assets/javascripts</code> area of the codebase and some in the new <code>app/javascript</code> area which is configured via Webpacker.</p>\n\n<p>As mentioned by others, I don't think we need to wholely re-write in TypeScript, but we should begin refactoring and writing new features this way. And in general, we should definitely be migrating the oldest JavaScript into the new area to whatever extent possible.</p>\n\n<p>I think this initiative can pretty effectively be led by the community rather than top down from our team, because we won't need to provide a lot of specific instruction in order to make improvements in these areas.</p>\n\n<p>Any pull requests to provide good instructions for this approach in the README and/or docs would be appreciated to get the ball rolling on this.</p>\n\n<p>Part of the reason I feel like we can get moving on some of this now is that GitPod might be useful for helping frontend developers get up and running with the codebase and making changes without the worry of installing and getting the app running locally.</p>\n\n\n<div class=\"ltag__link\">\n        <a href=\"/ben\" class=\"ltag__link__link\">\n          <div class=\"ltag__link__pic\">\n            <img src=\"https://res.cloudinary.com/practicaldev/image/fetch/s--RELHeEj1--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://res.cloudinary.com/practicaldev/image/fetch/s--Sb1rTJg1--/c_fill%2Cf_auto%2Cfl_progressive%2Ch_150%2Cq_auto%2Cw_150/https://thepracticaldev.s3.amazonaws.com/uploads/user/profile_image/1/f451a206-11c8-4e3d-8936-143d0a7e65bb.png\" alt=\"ben image\">\n          </div></a>\n          <a href=\"/ben/spin-up-a-local-instance-of-dev-in-the-cloud-with-gitpod-it-s-incredibly-simple-pij\" class=\"ltag__link__link\">\n            <div class=\"ltag__link__content\">\n              <h2>Spin up a \"local\" instance of DEV in the cloud with GitPod (It's incredibly simple)</h2>\n              <h3>Ben Halpern</h3>\n              <div class=\"ltag__link__taglist\">\n<span class=\"ltag__link__tag\">#contributorswanted</span><span class=\"ltag__link__tag\">#gitpod</span><span class=\"ltag__link__tag\">#opensource</span><span class=\"ltag__link__tag\">#docker</span>\n</div>\n            </div>\n        </a>\n      </div>\n\n\n<p>Only time will tell if GitPod leads to true productivity enhancements for frontend developers looking to contribute, but I think it's something worth exploring.</p>\n\n\n",
        "text": "I think the evolution and increased popularity of TypeScript over the past year or so means that it is a good time to migrate towards using it on DEV.\n\nNick Taylor has been the biggest proponent, but it all jives with my view of things.\n\nRead more here:\n\n\n\n        \n          \n            \n          \n          \n            \n              dev.to with a TypeScript or Flow frontend codebase?\n              Nick Taylor\n              \n#meta#javascript#typescript#flow\n\n            \n        \n      \n\n\nI did not want us to be too far on the bleeding edge of frontend technology and that continues to be my stance, but I think TypeScript is in a good place and Rails' support of \"modern\" JavaScript is likewise in a good place.\n\nAs it currently stands, we have some of our JavaScript in the \"old\" app/assets/javascripts area of the codebase and some in the new app/javascript area which is configured via Webpacker.\n\nAs mentioned by others, I don't think we need to wholely re-write in TypeScript, but we should begin refactoring and writing new features this way. And in general, we should definitely be migrating the oldest JavaScript into the new area to whatever extent possible.\n\nI think this initiative can pretty effectively be led by the community rather than top down from our team, because we won't need to provide a lot of specific instruction in order to make improvements in these areas.\n\nAny pull requests to provide good instructions for this approach in the README and/or docs would be appreciated to get the ball rolling on this.\n\nPart of the reason I feel like we can get moving on some of this now is that GitPod might be useful for helping frontend developers get up and running with the codebase and making changes without the worry of installing and getting the app running locally.\n\n\n\n        \n          \n            \n          \n          \n            \n              Spin up a \"local\" instance of DEV in the cloud with GitPod (It's incredibly simple)\n              Ben Halpern\n              \n#contributorswanted#gitpod#opensource#docker\n\n            \n        \n      \n\n\nOnly time will tell if GitPod leads to true productivity enhancements for frontend developers looking to contribute, but I think it's something worth exploring.",
        "categories": [],
        "sentiment": {
          "type": "positive",
          "score": 0.6428571428571429
        },    
        "tags": [
          "typescript",
          "device file",
          "bloodrock",
          "codebase",
          "javascript",
          "bleeding edge technology",
          "technology",
          "ruby on rails",
          "readme",
          "application software",
          "cloud computing",
          "open-source software",
          "docker (software)",
          "only time will tell (song)",
          "productivity software",
          "front and back ends"
        ]
      },
      "relationships": {
        "feed": {
          "data": {
            "id": "9036d02d-51fb-43bf-9012-c22e67beea7b",
            "type": "feed"
          }
        }
      }
    }
  ]
}
Enter fullscreen mode Exit fullscreen mode

PS. Token expires in 2 days. You can generate a new one. Take a look at doc.

there are still many things to improve :). Feel free to advise me and help me improve the service. If you like the project leave me a star :D.

Discussion

pic
Editor guide
Collapse
thejoezack profile image
Joe Zack

Hey, that's really sharp! I like that the api is nice and consistent and the elasticsearch is icing on the cake. Well done!