> For the complete documentation index, see [llms.txt](https://mukeshsolanki.gitbook.io/hashtag-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mukeshsolanki.gitbook.io/hashtag-api/reference/api-reference/hashtags.md).

# Hashtags

### Get Similar Hashtags

## Gets relevant hashtags based on the keyword provided as input

<mark style="color:blue;">`GET`</mark> `https://hashtag5.p.rapidapi.com/api/v2.1/tag/predict`

#### Query Parameters

| Name                                      | Type  | Description                                                |
| ----------------------------------------- | ----- | ---------------------------------------------------------- |
| keyword<mark style="color:red;">\*</mark> | insta | The keyword to use as a base to generate relavant hashtags |

#### Headers

| Name                                              | Type                    | Description                   |
| ------------------------------------------------- | ----------------------- | ----------------------------- |
| X-RapidAPI-Host<mark style="color:red;">\*</mark> | hashtag5.p.rapidapi.com | Should always be the host url |
| X-RapidAPI-Key<mark style="color:red;">\*</mark>  | YOUR\_API\_KEY          | Your API key                  |

{% tabs %}
{% tab title="200: OK Gets a list of similar hashtags" %}

```
{
    "tags": [
        "insta",
        "instagram",
        "instagood",
        "love",
        "instadaily",
        "follow",
        "like",
        "instalike",
        "photography",
        "photo",
        "likeforlikes",
        "photooftheday",
        "nature",
        "happy",
        "style",
        "likes",
        "life",
        "picoftheday",
        "art",
        "followforfollowback",
        "instamood",
        "model",
        "fashion",
        "india",
        "music",
        "beauty",
        "instapic",
        "cute",
        "viral",
        "selfie"
    ]
}
```

{% endtab %}
{% endtabs %}

Take a look at how you might call this method using our official libraries, or via `curl`:

{% tabs %}
{% tab title="Curl" %}

```bash
curl --request GET \
--url 'https://hashtag5.p.rapidapi.com/api/v2.1/tag/predict?keyword=insta' \
--header 'X-RapidAPI-Host: hashtag5.p.rapidapi.com' \
--header 'X-RapidAPI-Key: YOUR_API_KEY'
```

{% endtab %}
{% endtabs %}

### Get Trending Hashtags

## Gets a list of trending hashtags

<mark style="color:blue;">`GET`</mark> `https://hashtag5.p.rapidapi.com/api/v2.1/tag/trending`

#### Headers

| Name                                              | Type                    | Description                   |
| ------------------------------------------------- | ----------------------- | ----------------------------- |
| X-RapidAPI-Host<mark style="color:red;">\*</mark> | hashtag5.p.rapidapi.com | Should always be the host url |
| X-RapidAPI-Key<mark style="color:red;">\*</mark>  | YOUR\_API\_KEY          | Your API key                  |

{% tabs %}
{% tab title="200: OK a list of trending hashtags" %}

```json
{
    "tags": [
        "love",
        "followback",
        "instagramers",
        "envywear",
        "PleaseForgiveMe",
        "tweegram",
        "photooftheday",
        "20likes",
        "amazing",
        "smile",
        "follow4follow",
        "like4like",
        "look",
        "instalike",
        "igers",
        "picoftheday",
        "food",
        "instadaily",
        "instafollow",
        "followme",
        "girl",
        "instagood",
        "bestoftheday",
        "instacool",
        "envywearco",
        "follow",
        "colorful",
        "style",
        "swag",
        "fun",
        "model",
        "pretty",
        "nature",
        "lol",
        "dog",
        "hair",
        "sunset",
        "throwbackthursday",
        "beach",
        "friends",
        "hot",
        "funny",
        "blue",
        "life",
        "art",
        "photo",
        "cool",
        "clouds",
        "fitness",
        "all_shots",
        "textgram",
        "family",
        "instago",
        "igaddict",
        "awesome",
        "girls",
        "my",
        "bored",
        "baby",
        "music",
        "red",
        "green",
        "water",
        "black",
        "party",
        "white",
        "yum",
        "flower",
        "night",
        "instalove"
    ]
}
```

{% endtab %}
{% endtabs %}

Take a look at how you might call this method using our official libraries, or via `curl`:

{% tabs %}
{% tab title="Curl" %}

```bash
curl --request GET \
--url https://hashtag5.p.rapidapi.com/api/v2.1/tag/trending \
--header 'X-RapidAPI-Host: hashtag5.p.rapidapi.com' \
--header 'X-RapidAPI-Key: YOUR_API_KEY'
```

{% endtab %}
{% endtabs %}

### Getting Top Hashtags

## Gets Top Hashtags

<mark style="color:blue;">`GET`</mark> `https://hashtag5.p.rapidapi.com/api/v2.1/tag/top`

#### Headers

| Name                                              | Type                    | Description                   |
| ------------------------------------------------- | ----------------------- | ----------------------------- |
| X-RapidAPI-Host<mark style="color:red;">\*</mark> | hashtag5.p.rapidapi.com | Should always be the host url |
| X-RapidAPI-Key<mark style="color:red;">\*</mark>  | YOUR\_API\_KEY          | Your API key                  |

{% tabs %}
{% tab title="200: OK Top hashtags fetched successfully" %}

```json
{
    "tags": [
        "love",
        "instagood",
        "photooftheday",
        "fashion",
        "beautiful",
        "happy",
        "cute",
        "tbt",
        "like4like",
        "followme",
        "picoftheday",
        "follow",
        "me",
        "selfie",
        "summer",
        "art",
        "instadaily",
        "friends",
        "repost",
        "nature",
        "girl",
        "fun",
        "style",
        "smile",
        "food",
        "instalike",
        "family",
        "travel",
        "likeforlike",
        "fitness",
        "follow4follow",
        "igers",
        "tagsforlikes",
        "nofilter",
        "life",
        "beauty",
        "amazing",
        "instagram",
        "photography",
        "photo",
        "vscocam",
        "sun",
        "music",
        "followforfollow",
        "beach",
        "ootd",
        "bestoftheday",
        "sunset",
        "dog",
        "sky",
        "vsco",
        "l4l",
        "makeup",
        "foodporn",
        "f4f",
        "hair",
        "pretty",
        "cat",
        "model",
        "swag",
        "motivation",
        "girls",
        "party",
        "baby",
        "cool",
        "gym",
        "lol",
        "design",
        "instapic",
        "funny",
        "healthy",
        "christmas",
        "night",
        "lifestyle",
        "yummy",
        "flowers",
        "tflers",
        "hot",
        "handmade",
        "instafood",
        "wedding",
        "fit",
        "black",
        "일상",
        "pink",
        "blue",
        "workout",
        "work",
        "blackandwhite",
        "drawing",
        "inspiration",
        "holiday",
        "home",
        "london",
        "nyc",
        "sea",
        "instacool",
        "winter",
        "goodmorning",
        "blessed"
    ]
}
```

{% endtab %}
{% endtabs %}

Take a look at how you might call this method using our official libraries, or via `curl`:

{% tabs %}
{% tab title="Curl" %}

```bash
curl --request GET \
--url https://hashtag5.p.rapidapi.com/api/v2.1/tag/top \
--header 'X-RapidAPI-Host: hashtag5.p.rapidapi.com' \
--header 'X-RapidAPI-Key: YOUR_API_KEY'
```

{% endtab %}
{% endtabs %}

### Getting Post Count

## Gets a count of how many post are present on Instagram (Not realtime)

<mark style="color:blue;">`GET`</mark> `https://hashtag5.p.rapidapi.com/api/v2.1/tag/count`

#### Query Parameters

| Name                                  | Type  | Description                    |
| ------------------------------------- | ----- | ------------------------------ |
| tag<mark style="color:red;">\*</mark> | insta | The hashtag whos count we need |

#### Headers

| Name                                              | Type                    | Description                   |
| ------------------------------------------------- | ----------------------- | ----------------------------- |
| X-RapidAPI-Host<mark style="color:red;">\*</mark> | hashtag5.p.rapidapi.com | Should always be the host url |
| X-RapidAPI-Key<mark style="color:red;">\*</mark>  | YOUR\_API\_KEY          | Your API key                  |

{% tabs %}
{% tab title="200: OK The count fetched from Instagram" %}

```json
{
    "count": 149866852
}
```

{% endtab %}
{% endtabs %}

Take a look at how you might call this method using our official libraries, or via `curl`:

{% tabs %}
{% tab title="Curl" %}

```bash
curl --request GET \
--url 'https://hashtag5.p.rapidapi.com/api/v2.1/tag/top/count?tag=insta' \
--header 'X-RapidAPI-Host: hashtag5.p.rapidapi.com' \
--header 'X-RapidAPI-Key: YOUR_API_KEY'
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mukeshsolanki.gitbook.io/hashtag-api/reference/api-reference/hashtags.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.