Specify options (in the format of query string) in parameter `routeParams` parameter to extract data from JSON. | Key | Meaning | Accepted Values | Default | | ---------------- | ---------------------------------------- | --------------- | ------------------------------------------ | | `title` | The title of the RSS | `string` | Extracted from home page of current domain | | `item` | The JSON Path as `item` element | `string` | Entire JSON response | | `itemTitle` | The JSON Path as `title` in `item` | `string` | None | | `itemLink` | The JSON Path as `link` in `item` | `string` | None | | `itemLinkPrefix` | Optional Prefix for `itemLink` value | `string` | None | | `itemDesc` | The JSON Path as `description` in `item` | `string` | None | | `itemPubDate` | The JSON Path as `pubDate` in `item` | `string` | None | ::: tip JSON Path only supports format like `a.b.c`. if you need to access arrays, like `a[0].b`, you can write it as `a.0.b`. ::: Parameters parsing in the above example: | Parameter | Value | | ------------- | ------------------------------------------------------------------------ | | `url` | `https://api.github.com/repos/ginuerzh/gost/releases` | | `routeParams` | `title=Gost releases&itemTitle=tag_name&itemLink=html_url&itemDesc=body` | Parsing of `routeParams` parameter: | Parameter | Value | | ----------- | --------------- | | `title` | `Gost releases` | | `itemTitle` | `tag_name` | | `itemLink` | `html_url` | | `itemDesc` | `body` |

Specify options (in the format of query string) in parameter `routeParams` parameter to extract data from Sitemap. (Follows Sitemap Protocol 0.9) | Key | Meaning | Accepted Values | Default | | ------- | -------------------- | --------------- | -------------------------------- | | `title` | The title of the RSS | `string` | The first `<loc>` in the sitemap |

::: tip Filter parameters: - category: 100: trending, 200: newest, 300: top - status\_filter: 0: all, 100: available, 400: missed - community\_filter: 0: all community, 100: verified, 200: followed - rewards\_filter: 0: all rewards, 100: nft, 200: token, 400: whitelist - chain\_filter: 0: all chains, 1: ethereum, 56: bsc, 137: polygon, 42161: arb, 10: op, 324: zksync, 43114: avax - search: 'Search keyword', - count: 'Number of events to fetch', - page: 'Page number', :::

::: tip 路径处填写对应页面 URL 中 `http://www.qiyoujiage.com/` 和 `.shtml` 之间的字段。下面是一个例子。 若订阅 [福建漳州龙海今日油价](http://www.qiyoujiage.com/fujian/zhangzhou/longhai.shtml) 则将对应页面 URL <http://www.qiyoujiage.com/fujian/zhangzhou/longhai.shtml> 中 `http://www.qiyoujiage.com/` 和 `.shtml` 之间的字段 `fujian/zhangzhou/longhai` 作为路径填入。此时路由为 [`/qiyoujiage/fujian/zhangzhou/longhai`](https://rsshub.app/qiyoujiage/fujian/zhangzhou/longhai) :::

Latest badge pages from Peter Wunder's All Activity Challenges catalog. `pubDate` uses the first 'Visible in the app' date because the site does not expose a publication timestamp.

When applying a filter on <https://www.oevw.at/suche>, a POST request is sent to <https://www.oevw.at/suche/filter>. You can take its JSON body, URL-encode it (`encodeURIComponent('{...}')`) and append it to the URL, see example URL. for this route.

爬取巨量算数近 6 个月的头条指数，解密后提取指数波峰当日的热门搜索关键词，生成为 RSS。可用于追踪新闻热点事件。

爬取巨量算数近 6 个月的抖音指数，解密后提取指数波峰当日的热门搜索关键词，生成为 RSS。可用于追踪新闻热点事件。

There is an optional query parameter called `properties=` that can be used to customize field mapping. There are three built-in fields: author, pubTime and link, which can be used to add additional information. For example, if you have set up three properties in your database - "Publish Time", "Author", and "Original Article Link" - then execute the following JavaScript code to get the result for the properties parameter. ```js encodeURIComponent(JSON.stringify({"pubTime": "Publish Time", "author": "Author", "link": "Original Article Link"})) ``` There is an optional query parameter called `query=` that can be used to customize the search rules for your database, such as custom sorting and filtering rules. please refer to the [Notion API documentation](https://developers.notion.com/reference/post-database-query) and execute `encodeURIComponent(JSON.stringify(custom rules))` to provide the query parameter.

| [电子图书](http://read.nlc.cn/outRes/outResList?type=电子图书) | [电子期刊](http://read.nlc.cn/outRes/outResList?type=电子期刊) | [电子论文](http://read.nlc.cn/outRes/outResList?type=电子论文) | [电子报纸](http://read.nlc.cn/outRes/outResList?type=电子报纸) | [音视频](http://read.nlc.cn/outRes/outResList?type=音视频) | | -------------------------------------------------------------- | -------------------------------------------------------------- | -------------------------------------------------------------- | -------------------------------------------------------------- | ---------------------------------------------------------- | | [标准专利](http://read.nlc.cn/outRes/outResList?type=标准专利) | [工具书](http://read.nlc.cn/outRes/outResList?type=工具书) | [少儿资源](http://read.nlc.cn/outRes/outResList?type=少儿资源) | | -------------------------------------------------------------- | ---------------------------------------------------------- | -------------------------------------------------------------- |

1. If no specific parameters are specified, all subscription sources will be output by default. 2. Please obtain the Category ID or Subscription Source ID on the `Category` (shortcut `g` `c`) or `Source` (shortcut `g` `f`) page. The URL of each category (or subscription source) will display its ID information. 3. Support for category names and category IDs, to output multiple categories, please repeat entering `category=` and connect with `&`, or directly use **English** commas between different category names. For example, you can subscribe through `/miniflux/subscription/category=technology&category=1` or `/miniflux/subscription/categories=technology,1`. 4. Support specifying the subscription source name or subscription source ID, similar to setting categories. For example, you can subscribe through `/miniflux/subscription/feed=1&feed=Archdaily` or `/miniflux/subscription/feeds=1,Archdaily`. 5. Support simultaneously specifying subscription source information and category information; it will output subscription sources that meet the selected categories' criteria. Consider an example: by using `/miniflux/subscription/feeds=1,archdaily&category=art,7`, if the Subscription Source ID is 1 or the Subscription Source Name is ArchDaily indeed falls under Category 'art' or has a Category ID of 7, then output that subscription source information.