[Unofficial] Medium API Documentation
Tags: api, programming, webdev, tutorial
Published: 2023-09-09 07:08:16

Hey guys!

This is the "Getting Started" Guide for the **Medium API (Unofficial Version)**, listed on the [RapidAPI Platform](http://hub.mediumapi.com).

This REST API **_helps you to quickly extract data from_ [medium.com](https://medium.com)**, without any hassle.

{% youtube oc8TKG9EQfE %}

Using our Unofficial Medium API, you can get -

*   **User**'s - Info, Articles, Top Articles, Followers, Following, Interests, Lists, Publications

*   **Article**'s - Info, Responses, Content, Markdown, HTML, Fans, Related Articles

*   **Publication**'s - Info, Articles, Newsletter

*   **Top Feeds, Latest Posts, Top Writers, Tag Info, Related Tags**

*   **List's** - Info, Articles, Responses

*   **Search** - Articles, Publications, Users, Lists, Tags

> 💡 Checkout our **[swagger documentation](https://docs.mediumapi.com)** for the details on each endpoint!

* * *

Before getting started, you must first **[get your API Key](http://hub.mediumapi.com)** to authenticate your calls. You'll need to **pass it in the headers**, along with the requests, to use the API smoothly.

Header -

**x-rapidapi-key: \[RAPIDAPI\_KEY\]**

* * *

_Wondering how to subscribe to our API and get API Key? Watch the following video -_

{% youtube -MM1C6mb-mc %}

* * *

**API's Base URL:**

> https://medium2.p.rapidapi.com

* * *

**Endpoints:**

**User 👥  :**

· [GET User ID](#get-user-id)
· [GET User Info](#get-user-info)
· [GET User's Articles](#get-users-articles)
· [GET User's Top Articles](#get-users-top-articles)
· [GET User's Following](#get-users-following)
· [GET User's Followers](#get-users-followers)
· [GET User's Interests](#get-users-interests)
· [GET User's Lists](#get-users-list)
· [GET User's Publications](#get-users-publications)

**Article ✏️ :**

· [GET Article Info](#get-article-info)
· [GET Article's Content](#get-articles-content)
· [GET Article's Markdown](#get-articles-markdown)
· [GET Article's HTML](#get-articles-html)
· [GET Article's Responses](#get-articles-responses)
· [GET Article's Fans](#get-articles-fans)
· [GET Related Articles](#get-related-articles)

**Publication 📰  :**

· [GET Publication ID](#get-publication-id)
· [GET Publication Info](#get-publication-info)
· [GET Publication Articles](#get-publication-articles)
· [GET Publication's Newsletter](#get-publications-newsletter)

**Misc 🌀  :**

· [GET Latest Posts](#get-latest-posts)
· [GET Top Writers](#get-top-writers)
· [GET Top Feeds](#get-top-feeds)
· [GET Tag Info](#get-tag-info)
· [GET Related Tags](#get-related-tags)

**List 📜  :**

· [GET List Info](#get-list-info)
· [GET List Articles](#get-list-articles)
· [GET List Responses](#get-list-responses)

**Search 🔎  :**

· [Search Articles](#search-articles)
· [Search Publications](#search-publications)
· [Search User](#search-users)
· [Search Lists](#search-lists)
· [Search Tags](#search-tags)


* * *

GET User ID
-----------

Every Medium user has one unique hash ID associated with his/her account. Usually, we only deal with usernames that we choose while registering on Medium Platform. You can find your username in the sub-domain of your profile page URL or at the end of it. Like -

*   https:// **username** .medium.com
*   https:// medium.com/@ **username**

Once you get your username, like mine is _**nishu-jain,**_ you can use the following endpoint to get your `user_id`.

Endpoint -

> GET /user/id\_for/{username}

Usage -

Once you have the `user_id`, you can invoke other user-related endpoints using it.

{% gist https://gist.github.com/weeping-angel/ac33f3d869ea8a859052fbb98e988385 file=user_id.sh %}

{% gist https://gist.github.com/weeping-angel/ac33f3d869ea8a859052fbb98e988385 file=user_id_output.txt %}

* * *

GET User Info
-------------

Once you've got the `user_id`, you can use it to get user-related information such as - _Full name, Username, Bio, Followers & Following count, Twitter username, Profile-image, top writer status, etc ..._

Endpoint -

> GET /user/{user_id}

If you don't have the `user_id`, see the _**[GET User ID](#get-user-id)**_ endpoint above.

Usage -

{% gist https://gist.github.com/weeping-angel/c26f5b68a01c5482f5a712e0a652fdd3 file=user_info.sh %}

{% gist https://gist.github.com/weeping-angel/c26f5b68a01c5482f5a712e0a652fdd3 file=user_info_output.txt %}

* * *

GET User's Articles
-------------------

This endpoint returns a list of articles (`article_ids`) written by the Medium user.

> 💡 You can then use the **[GET Article Info](#get-article-info)** endpoint to retrieve information, such as _title, subtitle, author, claps, voters, tags, topics, publication, etc...,_ related to your desired article.

Endpoint -

> GET /user/{user_id}/articles

Usage -

{% gist https://gist.github.com/weeping-angel/c0c133d64268a9ef2a4eb62e0408f474 file=user_articles.sh %}

{% gist https://gist.github.com/weeping-angel/c0c133d64268a9ef2a4eb62e0408f474 file=user_articles_output.txt %}

* * *

GET User's Top Articles
-----------------------

This endpoint returns a list of `aritcle_ids` of the top 10 posts/articles on the user's profile (usually in chronological order - most recent posts), for the given user (`user_id`).

> 💡 You can then use the **[GET Article Info](#get-article-info)** endpoint to retrieve information on individual articles.

Endpoint -

> GET /user/{user_id}/top_aritcles

Usage -

{% gist https://gist.github.com/weeping-angel/c64fb4791441951deeaaac458672879b file=user_top_articles.sh %}

{% gist https://gist.github.com/weeping-angel/c64fb4791441951deeaaac458672879b file=user_top_articles_output.txt %}

* * *

GET User's Following
--------------------

This endpoint returns a list of `user_ids` of the given user's followings.

You can fetch this list and use the **[GET User Info](#get-user-info)** endpoint to retrieve information related to the individual users.

> **Note:** Currently, this list does not contain the `publication_ids` of the publications that the user is following.

**Query Parameters _(Optional)_: -**

*   **`count`**: To limit the number of results. (`count` <= 1500)

Endpoint -

> GET /user/{user_id}/following

Usage —

{% gist https://gist.github.com/weeping-angel/7f3d13b52205e5b48a0edba8a8677bfe file=user_following.sh %}

{% gist https://gist.github.com/weeping-angel/7f3d13b52205e5b48a0edba8a8677bfe file=user_following_output.txt %}

* * *

GET User's Followers
--------------------

This endpoint returns a list of `user_ids` of the followers for the given user.

> **Note:** The length of followers' list might be different from what you get in the **[Get User Info](#get-user-info)** Endpoint. It's because, this list doesn't include Medium Users who left the platform.
> 
> If you really need the exact followers' count, use this endpoint to get the followers' list and take its length as the exact followers' count

You can use the **[GET User Info](#get-user-info)** endpoint to retrieve information related to the individual users.

**Query Parameters _(Optional)_: -**

*   **`count`**: To limit the number of results. (`count` <= 1500)

Endpoint -

> GET /user/{user_id}/followers

Usage -

{% gist https://gist.github.com/weeping-angel/66e7ee163f48e426dec93fbded420802 file=user_followers.sh %}

{% gist https://gist.github.com/weeping-angel/66e7ee163f48e426dec93fbded420802 file=user_followers_output.txt %}

* * *

GET User's Interests
--------------------

This endpoint returns a list of **`tags`** that the given user follows on Medium.

> All tags are lowercased hyphen-separated strings.

Endpoint -

> GET /user/{user_id}/interests

Usage —

{% gist https://gist.github.com/weeping-angel/deb68d4ac20f29fae389bc78d2bab6a4 file=user_interests.sh %}

{% gist https://gist.github.com/weeping-angel/deb68d4ac20f29fae389bc78d2bab6a4 file=user_interests_output.txt %}

* * *

GET User's Lists
----------------

This endpoint returns an array of **`list_ids`** created by the user.

> You can use the **[GET List Info](#get-list-info)** endpoint to retrieve information on individual Medium Lists.

Endpoint -

> GET /user/{user_id}/lists

Usage -

{% gist https://gist.github.com/weeping-angel/42ae06edabb0fc32d8047356b88685ab file=user_lists.sh %}

{% gist https://gist.github.com/weeping-angel/42ae06edabb0fc32d8047356b88685ab file=user_lists_output.txt %}

* * *

GET User's Publications
-----------------------

This endpoint returns a list of **`publication_ids`** where the user is the editor and/or creator.

> You can use the **[GET Publication Info](#get-publication-info)** endpoint to retrieve information on individual publications.

Endpoint -

> GET /user/{user_id}/publications

Usage -

{% gist https://gist.github.com/weeping-angel/177663bcaf85d98d3504a6df8889714e file=user_publications.sh %}

{% gist https://gist.github.com/weeping-angel/177663bcaf85d98d3504a6df8889714e file=user_publications_output.txt %}

* * *

GET Article Info
----------------

This endpoint returns the article-related information such as _Title, Subtitle, Author, Tags, Topics_ (as assigned by Medium), _Publication, Published date and time, Clap Count, Voter Count, Word Count, Responses Count, Reading Time, Language, etc..._

For using this endpoint, you'll need an article's unique hash ID, called `article_id`.

You can find the `article_id` at the end of any Medium Story's URL. Like -

*   https:// medium.com /towards-artificial-intelligence/why-its-super-hard-to-be-an-ml-researcher-or-developer- **67fa62fc1971**
*   https:// nishu-jain.medium.com /the-neutrality-of-death- **20abb01e5c85**

Endpoint -

> GET /article/{article_id}

Usage -

{% gist https://gist.github.com/weeping-angel/3946e149d9b99b00e16fca59845ea2d3 file=article_info.sh %}

{% gist https://gist.github.com/weeping-angel/3946e149d9b99b00e16fca59845ea2d3 file=article_info_output.txt %}

* * *

GET Article's Content
---------------------

This endpoint returns the textual content of an article/story, for the corresponding `article_id`.

> You can get the `article_id` from the URL, as shown above in the **[GET Article Info](#get-article-info)** endpoint.

Endpoint -

> GET /article/{article\_id}/content

Usage -

{% gist https://gist.github.com/weeping-angel/d64a3b2a09ad468abc517949379b1c0b file=article_content.sh %}

{% gist https://gist.github.com/weeping-angel/d64a3b2a09ad468abc517949379b1c0b file=article_content_output.txt %}

* * *

GET Article's Markdown
----------------------

This endpoint returns the article content in the markdown format (_.md_), for the corresponding `article_id`.

> You can get the `article_id` from the URL, as shown above in the **[GET Article Info](#get-article-info)** endpoint.

Endpoint -

> GET /article/{article_id}/markdown

Usage -

{% gist https://gist.github.com/weeping-angel/a692fc43a7f8a85aa25e358baf0544d6 file=article_markdown.sh %}

{% gist https://gist.github.com/weeping-angel/a692fc43a7f8a85aa25e358baf0544d6 file=article_markdown_output.txt %}

* * *

GET Article's HTML
------------------

This endpoint returns the article in plain HTML format (_.html_), for the corresponding `article_id`.

> You can get the _`article_id`_ from the URL, as shown above in the **[GET Article Info](#get-article-info)** endpoint.

**Query Parameter (_Optional_) : -**

*   Set **`fullpage`** parameter to **`true`** to get the full HTML page with head, body, title and meta tags. If `fullpage` is set to `false` or not provided, the endpoint will only return the HTML inside body tag.

Endpoint -

> GET /article/{article_id}/html

> GET /article/{article_id}/html?fullpage=true

Usage -

{% gist https://gist.github.com/weeping-angel/7a2ccc872b043fd0113fe418515a8631 file=article_html.sh %}

{% gist https://gist.github.com/weeping-angel/7a2ccc872b043fd0113fe418515a8631 file=article_html_output.txt %}

* * *

GET Article's Responses
-----------------------

This endpoint returns a list of responses (`response_ids`, same as `article_ids`) for a given article (`article_id`)

> **Note:** You can treat `response_id` pretty much same as `aritcle_id`. To see the content of the response, use the **[Get Article's Content](#get-articles-content)** endpoint.

Endpoint -

> GET /article/{article_id}/responses

Usage -

{% gist https://gist.github.com/weeping-angel/5e7b360bd7e3a03e3035a036a50e22c8 file=article_responses.sh %}

{% gist https://gist.github.com/weeping-angel/5e7b360bd7e3a03e3035a036a50e22c8 file=article_responses_output.txt %}

* * *

GET Article's Fans
------------------

This endpoint returns a list of `user_ids` of the people who clapped on the article.

> You can use the **[GET User Info](#get-user-info)** endpoint to retrieve information on individual users.

Endpoint -

> GET /article/{article\_id}/fans

Usage -

{% gist https://gist.github.com/weeping-angel/dc15a0310469816a9b0317b975da24a8 file=article_fans.sh %}

{% gist https://gist.github.com/weeping-angel/dc15a0310469816a9b0317b975da24a8 file=article_fans_output.txt %}

* * *

GET Related Articles
--------------------

This endpoint returns a list of `article_ids` of the related posts. _(Length = 5)_

> **Note:** If the article is self-published, related posts will belong to the same author. Else, related posts will belong to the publication in which the article is published.

Endpoint -

> GET /article/{article_id}/related

Usage -

{% gist https://gist.github.com/weeping-angel/8157dcb20427892dfe12d06ef3406217 file=related_articles.sh %}

{% gist https://gist.github.com/weeping-angel/8157dcb20427892dfe12d06ef3406217 file=related_articles_output.txt %}

* * *

GET Publication ID
------------------

Every Medium Publication has one unique hash ID associated with it. Usually, we only deal with **`publication_slug`** that is generated when we choose our Publication's Name. You can find your `publication_slug` in the homepage URL of your publication. Like -

*   https:// medium.com / **publication_slug**

Once you get your `publication_slug`, you can use the following endpoint to get your **`publication_id`**.

Endpoint -

> GET /publication/id_for/{publication_slug}

Usage -

{% gist https://gist.github.com/weeping-angel/dbd1ee3e532789a662f85b54a9449bdc file=publication_id.sh %}

{% gist https://gist.github.com/weeping-angel/dbd1ee3e532789a662f85b54a9449bdc file=publication_id_output.txt %}

* * *

GET Publication Info
--------------------

This endpoint returns publication-related information such as _Publication name, Tagline, Description, Tags, Followers Count, Creator, Editors, Twitter username, Instagram username, Facebook Page name, Logo, Domain, etc ..._ for the corresponding `publication_id`.

A `publication_id` is the unique hash ID associated with every Medium Publication. For example, `publication_id` of [TowardsDataScience](http://towardsdatascience.com/) is _"7f60cf5620c9"_

If you don't know the `publication_id`, you can get it from any article published under it. Use the endpoint **[GET Article Info](#get-article-info),** to retrieve the `publication_id`. Or, if you know the `publication_slug`, use the endpoint **[GET Publication ID](#get-publication-id)**.

Endpoint -

> GET /publication/{publication_id}

Usage -

{% gist https://gist.github.com/weeping-angel/e73f4c180b71fed2de9160dff38d25be file=publication_info.sh %}

{% gist https://gist.github.com/weeping-angel/e73f4c180b71fed2de9160dff38d25be file=publication_info_output.txt %}

* * *

GET Publication Articles
------------------------

This endpoint returns the list of `articles_ids` of the latest 25 articles, posted recently in that publication.

> You can use the **[GET Article Info](#get-article-info)** endpoint to retrieve information on individual articles.

**Query Parameter _(Optional): -_**

*   **`from`**: Use the **`from`** query parameter to get the articles before that date and time.

Endpoint -

> GET /publication/{publication_id}/articles

Usage -

{% gist https://gist.github.com/weeping-angel/d4ba88bd29cf3482927e77e87ed236d7 file=publication_articles.sh %}

{% gist https://gist.github.com/weeping-angel/d4ba88bd29cf3482927e77e87ed236d7 file=publication_articles_output.txt %}

* * *

GET Publication's Newsletter
----------------------------

This endpoint returns information related to the associated newsletter for the given publication. This includes their _name, description, creator's id_, _subscriber's count, unique id, image url, etc..._

Endpoint -

> GET /publication/{publication_id}/newsletter

Usage -

{% gist https://gist.github.com/weeping-angel/4ed062ced5c2068cec38567f62d497f4 file=publication_newsletter.sh %}

{% gist https://gist.github.com/weeping-angel/4ed062ced5c2068cec38567f62d497f4 file=publication_newsletter_output.txt %}

* * *

GET Latest Posts
----------------

This endpoint returns a list of the latest posts (`article_ids`) under a topic/niche (as classified and **distributed** by the Medium platform). Examples of a topic/niche can be:

*   blockchain
*   artificial-intelligence
*   relationships
*   mental-health, etc ...

These are known as `topic_slugs`. (Not same as `tags`)

At any given moment, this endpoint will return a list of 25 articles (`article_ids`). You can then **[GET Article Info](#get-article-info)** endpoint to retrieve information related to each article.

Endpoint -

> GET /latestposts/{topic_slug}

Usage -

{% gist https://gist.github.com/weeping-angel/dad4f1382928798b5d2dbfd1fd9c8c38 file=latestposts.sh %}

{% gist https://gist.github.com/weeping-angel/dad4f1382928798b5d2dbfd1fd9c8c38 file=latestposts_output.txt %}

* * *

GET Top Writers
---------------

This endpoint returns a list of top writers (`user_ids`) within a particular topic/niche (using `topic_slug`). Examples of `topic_slug` are -

*   blockchain
*   relationships
*   artificial-intelligence, etc ...

You can use an optional query parameter `count` to specify the number of top writers you want to retrieve.

> **Note:** Maximum number of top writers within a topic will be 250.

After fetching the `user_ids`, you can use the **[GET User Info](#get-user-info)** endpoint to extract information related to the individual users.

Endpoint -

> GET /top_writers/{topic_slug}

> GET /top_writers/{topic_slug}?count={count}

Usage —

{% gist https://gist.github.com/weeping-angel/9217562c854f85a2c949fb497ceb8cbc file=top_writers.sh %}

{% gist https://gist.github.com/weeping-angel/9217562c854f85a2c949fb497ceb8cbc file=top_writers_output.txt %}

* * *

GET Top Feeds
-------------

This endpoint returns a list of `article_ids` (default count = 25) for the given `tag` and `mode`.

Example of a `tag` will _‘blockchain', ‘defi', ‘artificial-intelligence', etc..._

Mode:

*   `hot` : For getting trending articles
*   `new` : For getting the latest articles
*   `top_year` : For getting the best articles of the year
*   `top_month` : For getting the best articles of the month
*   `top_week` : For getting the best articles of the week
*   `top_all_time`: For getting the best articles of all time

> **Note:** You can use the **[GET Article Info](#get-article-info)** endpoint to retrieve information related to each article.

**Query Parameters (_Optional_): -**

*   To get the subsequent top feeds, it can also take a query string parameter called **`after`**, where, `after` < 250.
*   To limit the number of top feeds, use another query string parameter called **`count`**, where `count` < 25.

Endpoint -

> GET /topfeeds/{tag}/{mode}

Usage -

{% gist https://gist.github.com/weeping-angel/8be504accef43976d161cd0b72c23009 file=topfeeds.sh %}

{% gist https://gist.github.com/weeping-angel/8be504accef43976d161cd0b72c23009 file=topfeeds_output.txt %}

* * *

Get Tag Info
------------

This endpoint returns tag-related information for the given `tag`. This includes:

*   Tag Name
*   Followers Count
*   Number of stories
*   Number of writers
*   Number of latest stories
*   Number of latest writers

> **Note:** **`tags`** are lowercased, hyphen-separated strings representing a category or niche on Medium Platform

Endpoint -

> GET /tag/{tag}

Usage -

{% gist https://gist.github.com/weeping-angel/03c46c14b2e9be11ca61d724dad3694d file=tag_info.sh %}

{% gist https://gist.github.com/weeping-angel/03c46c14b2e9be11ca61d724dad3694d file=tag_info_output.txt %}

* * *

Get Related Tags
----------------

This endpoint returns a list of **`related_tags`** for a given `tag`.

**Example:** For the tag `blockchain`, it will return _"cryptocurrency", "bitcoin", "ethereum", "crypto", "ico", "technology", "defi", "nft", "fintech"_.

Endpoint -

> GET /related_tags/{tag}

Usage -

{% gist https://gist.github.com/weeping-angel/6a0628389b1b1b27b9cc893c7c0181f4 file=related_tags.sh %}

{% gist https://gist.github.com/weeping-angel/6a0628389b1b1b27b9cc893c7c0181f4 file=related_tags_output.txt %}

* * *

GET List Info
-------------

This endpoint returns the Medium's _**list-related**_ information - such as _id, name, author, description, thumbnail image url, creation datetime, last modified datetime, number of articles in the list, claps, voters, and comments -_ for the given `list_id`_._

The `list_id` is the unique hash ID associated with every Medium List. You can see it at the end of the URL as follows:

*   https:// nishu-jain.medium.com /list/medium-api-**38f9e0f9bea6**

Here **`38f9e0f9bea6`** is the `list_id`.

Endpoint -

> GET /list/{list_id}

Usage -

{% gist https://gist.github.com/weeping-angel/f3c985b9626491950f379d25ea0c7e12 file=list_info.sh %}

{% gist https://gist.github.com/weeping-angel/f3c985b9626491950f379d25ea0c7e12 file=list_info_output.txt %}

* * *

GET List Articles
-----------------

This endpoint returns an array of `article_ids` present in the given Medium List.

> You can use the **[GET Article Info](#get-article-info)** endpoint to retrieve information on individual articles.

Endpoint -

> GET /list/{list_id}/articles

Usage -

{% gist https://gist.github.com/weeping-angel/8c5fcebc9b90574209a00fe82651dc8b file=list_articles.sh %}

{% gist https://gist.github.com/weeping-angel/8c5fcebc9b90574209a00fe82651dc8b file=list_articles_output.txt %}

* * *

GET List Responses
------------------

This endpoint returns an array of `response_ids` for the given Medium List.

> **Note:** You can treat `response_id` pretty much same as `aritcle_id`. To see the content of the response, use the **[Get Article's Content](#get-articles-content)** endpoint.

Endpoint -

> GET /list/{list_id}/responses

Usage -

{% gist https://gist.github.com/weeping-angel/e6668982cef713eff2ac41e95013d442 file=list_responses.sh %}

{% gist https://gist.github.com/weeping-angel/e6668982cef713eff2ac41e95013d442 file=list_responses_output.txt %}

* * *

Search Articles
---------------

This endpoint returns a list of **`article_ids`** that match the search query. The maximum length of this list will be 1000. If no articles are found that match the search query, then an empty list will be returned.

**Query Parameter _(Required)_: -**

*   **`query`**: A string parameter that specifies the search query for which the articles need to be retrieved.

> You can use the **[GET Article Info](#get-article-info)** endpoint to retrieve information on individual articles.

Endpoint -

> GET /search/articles?query={query}

Usage -

{% gist https://gist.github.com/weeping-angel/11c71118c79feeb2deea8552c77ca04c file=search_articles.sh %}

{% gist https://gist.github.com/weeping-angel/11c71118c79feeb2deea8552c77ca04c file=search_articles_output.txt %}

* * *

Search Publications
-------------------

This endpoint returns a list of **`publication_ids`** that match the search query. The maximum length of this list will be 1000. If no publications are found that match the search query, then an empty list will be returned.

**Query Parameter _(Required)_: -**

*   **`query`**: A string parameter that specifies the search query for which the publications need to be retrieved.

> You can use the **[GET Publication Info](#get-publication-info)** endpoint to retrieve information on individual publications.

Endpoint -

> GET /search/publications?query={query}

Usage -

{% gist https://gist.github.com/weeping-angel/e24d6a9462175e8df40d11fec1d60a05 file=search_publications.sh %}

{% gist https://gist.github.com/weeping-angel/e24d6a9462175e8df40d11fec1d60a05 file=search_publications_output.txt %}

* * *

Search Users
------------

This endpoint returns a list of **`user_ids`** that match the search query. The maximum length of this list will be 1000. If no users are found that match the search query, then an empty list will be returned.

**Query Parameter _(Required): -_**

*   **`query`**: A string parameter that specifies the search query for which the users need to be retrieved.

> You can use the **[GET User Info](#get-user-info)** endpoint to retrieve information on individual users.

Endpoint -

> GET /search/users?query={query}

Usage -

{% gist https://gist.github.com/weeping-angel/f5e63f8b87fb284d3562390093ac71a5 file=search_users.sh %}

{% gist https://gist.github.com/weeping-angel/f5e63f8b87fb284d3562390093ac71a5 file=search_users_output.txt %}

* * *

Search Lists
------------

This endpoint returns an array of **`list_ids`** that match the search query. The maximum length of this array will be 1000. If no Medium Lists are found that match the search query, then an empty array will be returned.

**Query Parameter _(Required): -_**

*   **`query`**: A string parameter that specifies the search query for which the Medium Lists need to be retrieved.

> You can use the **[GET List Info](#get-list-info)** endpoint to retrieve information on individual Medium Lists.

Endpoint -

> GET /search/lists?query={query}

Usage -

{% gist https://gist.github.com/weeping-angel/21a7f30b191462850d236f55afb0fd23 file=search_lists.sh %}

{% gist https://gist.github.com/weeping-angel/21a7f30b191462850d236f55afb0fd23 file=search_lists_output.txt %}

* * *

Search Tags
-----------

This endpoint returns a list of **`tags`** that match the search query. The maximum length of this list will be 1000. If no tags are found that match the search query, then an empty list will be returned.

**Query Parameter _(Required)_: -**

*   **`query`**: A string parameter that specifies the search query for which the tags need to be retrieved.

Endpoint -

> GET /search/tags?query={query}

Usage -

{% gist https://gist.github.com/weeping-angel/af8db800bc22ad5b226d58d5314a514b file=search_tags.sh %}

{% gist https://gist.github.com/weeping-angel/af8db800bc22ad5b226d58d5314a514b file=search_tags_output.txt %}

* * *

Final thoughts -
----------------

As of now, this API consists of 33 endpoints, all of which use the GET method. I'll try to add more endpoints in the future and improve its efficiency to provide you with the best Unofficial Medium API possible.

*   You can subscribe to this API here: **[Medium API - RapidAPI](http://hub.mediumapi.com)**
*   Read its Swagger documentation here: **[API Documentation](https://docs.mediumapi.com)**
*   And if you're a python programmer, do **`pip install medium-api`**. Visit the following link to know more about Unofficial Medium API's Python SDK.

[GitHub - weeping-angel/medium-api](https://github.com/weeping-angel/medium-api)

If you've any thoughts on it, feel free to share them. I'll appreciate your feedback and try to improve it further.

My email ID: _**<nishu@mediumapi.com>**_

_Thanks for reading and have a wonderful day!_

* * *

**PS:** We post tutorials, videos, code snippets, and insights related to Medium and Unofficial Medium API. So be sure to follow us on:

*   Twitter: **[twitter.com/medium\_api](https://twitter.com/medium_api)**
*   LinkedIn: **[www.linkedin.com/company/medium-api](https://www.linkedin.com/company/medium-api)**