Name: Living Slang Decoder API
Brand: nicheapi-llc-1
SKU: api-nicheapi-llc-1-slangdecoder
Availability: InStock
Author: API Market

True Scary Stories

# Living Slang Decoder API

## Overview
The Living Slang Decoder API is a curated slang intelligence database covering 160+ real slang terms across five generations — Gen Alpha, Gen Z, Millennial, Gen X, and Boomer — each tagged with a living status (rising, peak, cringe, or dead), generation association, brand safety rating, and an "over 25" usage flag. Unlike general-purpose slang references that define what a term means, this API tells you whether it is still socially viable — making it the only programmatic source that distinguishes currently trending slang from terms that have already become cringe or dead. A reverse-translation endpoint maps plain English words and phrases to their current slang equivalents, and a trending endpoint surfaces the 33 terms gaining momentum this month with direction and score data. The dataset is sourced from TikTok, Twitter, Twitch, hip-hop lyrics, ballroom and queer culture, AAVE, and gaming communities, verified against Urban Dictionary, Know Your Meme, and social media usage frequency.

## Features

*   **160+ Slang Terms**: Covers terms across five generations with meaning, origin, first-seen year, usage example, and a popularity score (0–100) for each entry.
*   **4 Living Status Levels**: Every term is classified as `rising` (gaining traction), `peak` (at maximum usage), `cringe` (past its prime but still in circulation), or `dead` (no longer in active use) — the core differentiator from static slang references.
*   **Brand Safety Ratings**: Each term carries a `safe`, `caution`, `risky`, or `toxic` brand safety rating, enabling automated screening for marketing and content moderation workflows.
*   **"Over 25" Flag**: 50 terms are tagged with `over_25_flag: true`, identifying slang that reads as inauthentic or embarrassing when used by older speakers.
*   **Generation Association**: Every term is mapped to its primary generation — Gen Alpha, Gen Z, Millennial, Gen X, or Boomer — for audience targeting and content calibration.
*   **Reverse Translation**: Submit plain English text and receive current slang equivalents, covering 44 translation pairs across emotions, actions, and judgments.
*   **Monthly Trending Data**: 33 terms tracked with current direction, popularity score, and week-over-week change — updated monthly.
*   **Batch Translation**: Submit multiple English phrases for slang translation in a single request.
*   **Category & Status Reference**: A dedicated endpoint lists all available categories and status levels for use in filtering and UI construction.

## Use Cases

The Living Slang Decoder API is suited for a range of marketing, moderation, content, and consumer application workflows:

*   **Social Media Management Tools**: Screen campaign copy for dead or toxic slang before publishing to youth audiences. The brand safety rating and living status together provide a two-signal filter for content approval workflows.
*   **Marketing Agencies**: Validate slang usage in Gen Z and Gen Alpha campaigns without relying on manual research or internal cultural consultants — flagging cringe or dead terms before they reach the client review stage.
*   **Content Moderation Platforms**: Identify risky or toxic slang in user-generated content using the brand safety rating as a structured classification signal.
*   **Parental Control Apps**: Monitor and flag risky slang terms in messages, posts, or search history using the `brand_safety` and `over_25_flag` fields to surface terms parents may be unfamiliar with.
*   **Chatbot & Conversational AI Builders**: Generate natural-sounding, generationally accurate slang responses by querying living status and generation before selecting terms for bot output.
*   **Localization & Translation Services**: Verify slang currency before including terms in localized content — ensuring translated material uses currently active vocabulary rather than terms that have already cycled out.


## API Documentation

### Base URL
All API requests for the Living Slang Decoder API should be made to the following base URL:
`https://prod.api.market/api/v1/nicheapi-llc-1/slangdecoder/v1/slangdecoder`

### Authentication
Authentication is handled via an API key obtained from RapidAPI. Include your key in the `x-api-market-key` header of every request:

```
x-api-market-key: YOUR_API_KEY
```

Replace `YOUR_API_KEY` with your actual API key from RapidAPI.


### Endpoints

#### 1. Look Up a Slang Term

Retrieve the full profile for a specific slang term — including meaning, origin, living status, generation, brand safety rating, over-25 flag, usage example, and popularity score.

**Method**: `GET`
**Endpoint**: `/v1/slangdecoder/term/{word}`

**Parameters**:

| Name | In | Description | Type | Required |
| :--- | :--- | :--- | :--- | :--- |
| `word` | path | The slang term to look up | `string` | Yes |

**Example Request**:

```bash
curl -X GET "https://prod.api.market/api/v1/nicheapi-llc-1/slangdecoder/v1/slangdecoder/term/gyatt" \
  -H "x-api-market-key: YOUR_API_KEY"
```

**Example Response (200 OK)**:

```json
{
  "term": "gyatt",
  "match_type": "exact",
  "meaning": "Exclamation of surprise or attraction",
  "origin": "TikTok/streamer culture",
  "first_seen": "2022",
  "status": "rising",
  "generation": "Gen Alpha",
  "brand_safety": "risky",
  "over_25_flag": true,
  "usage_example": "*sees photo* Gyatt!",
  "popularity_score": 92
}
```

#### 2. Translate English to Slang

Submit a plain English word or phrase and receive current slang equivalents. Covers 44 translation pairs across emotions, actions, and judgments.

**Method**: `POST`
**Endpoint**: `/v1/slangdecoder/translate`

**Request Body**:

| Name | In | Description | Type | Required |
| :--- | :--- | :--- | :--- | :--- |
| `text` | body | The plain English word or phrase to translate | `string` | Yes |

**Example Request**:

```bash
curl -X POST "https://prod.api.market/api/v1/nicheapi-llc-1/slangdecoder/v1/slangdecoder/translate" \
  -H "x-api-market-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text": "excellent"}'
```

#### 3. Batch Translate English to Slang

Submit multiple plain English phrases for slang translation in a single request.

**Method**: `POST`
**Endpoint**: `/v1/slangdecoder/translate/batch`

**Request Body**:

| Name | In | Description | Type | Required |
| :--- | :--- | :--- | :--- | :--- |
| `phrases` | body | Array of plain English strings to translate | `array` | Yes |

**Example Request**:

```bash
curl -X POST "https://prod.api.market/api/v1/nicheapi-llc-1/slangdecoder/v1/slangdecoder/translate/batch" \
  -H "x-api-market-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"phrases": ["excellent", "embarrassing", "attractive person"]}'
```

#### 4. Get Trending Terms

Retrieve the 33 currently trending terms with their living status, popularity score, direction, and week-over-week change. Updated monthly.

**Method**: `GET`
**Endpoint**: `/v1/slangdecoder/trending`

**Example Request**:

```bash
curl -X GET "https://prod.api.market/api/v1/nicheapi-llc-1/slangdecoder/v1/slangdecoder/trending" \
  -H "x-api-market-key: YOUR_API_KEY"
```

#### 5. Run Test Scenarios

Generate random sample term lookups for development and schema validation.

**Method**: `POST`
**Endpoint**: `/v1/slangdecoder/test`

**Request Body**:

| Name | In | Description | Type | Required | Default |
| :--- | :--- | :--- | :--- | :--- | :--- |
| `count` | body | Number of random term samples to return | `integer` | No | `1` |

**Example Request**:

```bash
curl -X POST "https://prod.api.market/api/v1/nicheapi-llc-1/slangdecoder/v1/slangdecoder/test" \
  -H "x-api-market-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"count": 3}'
```

#### 6. List Categories and Statuses

Retrieve all available term categories and status levels for use in filtering and UI construction.

**Method**: `GET`
**Endpoint**: `/v1/slangdecoder/categories`

**Example Request**:

```bash
curl -X GET "https://prod.api.market/api/v1/nicheapi-llc-1/slangdecoder/v1/slangdecoder/categories" \
  -H "x-api-market-key: YOUR_API_KEY"
```

#### 7. Get Database Statistics

Retrieve aggregate statistics across the full slang database — term counts by status, generation, brand safety rating, and over-25 flag.

**Method**: `GET`
**Endpoint**: `/v1/slangdecoder/stats`

**Example Request**:

```bash
curl -X GET "https://prod.api.market/api/v1/nicheapi-llc-1/slangdecoder/v1/slangdecoder/stats" \
  -H "x-api-market-key: YOUR_API_KEY"
```

#### 8. Health Check

Check API availability and retrieve service status.

**Method**: `GET`
**Endpoint**: `/v1/slangdecoder/health`

**Example Request**:

```bash
curl -X GET "https://prod.api.market/api/v1/nicheapi-llc-1/slangdecoder/v1/slangdecoder/health" \
  -H "x-api-market-key: YOUR_API_KEY"
```

#### 9. API Overview

Returns the API welcome message and a map of available endpoints. 

**Method**: `GET`
**Endpoint**: `/v1/slangdecoder/`

**Example Request**:

```bash
curl -X GET "https://prod.api.market/api/v1/nicheapi-llc-1/slangdecoder/v1/slangdecoder/"
```


## Status Codes
Below is a list of common HTTP status codes you may encounter when interacting with the Living Slang Decoder API:

*   **`200 OK`**: The request was successful and the server has returned the requested data.
*   **`400 Bad Request`**: The server could not process the request due to invalid input — such as a missing `text` field in a translate request or a malformed batch array. Review your request body before retrying.
*   **`401 Unauthorized`**: Authentication failed. Your `x-api-market-key` header is missing or contains an invalid key. Confirm your key is active and correctly included in the request header.
*   **`404 Not Found`**: The requested slang term does not exist in the database, or the endpoint path is incorrect. Verify the term spelling and URL path against the endpoint reference above.
*   **`429 Too Many Requests`**: You have exceeded your plan's rate limit. Implement client-side rate limiting and exponential backoff. Check the `Retry-After` response header for guidance on when to retry.
*   **`500 Internal Server Error`**: An unexpected server-side error occurred. Retry the request after a short delay.
*   **`503 Service Unavailable`**: The server is temporarily unavailable due to maintenance or elevated load. Retry after a short delay.

## Rate Limits
The Living Slang Decoder API enforces a rate limit of **60 requests per minute** across all plans.

If you exceed this limit, the API returns a `429 Too Many Requests` status code. Implement exponential backoff in your client and monitor the `Retry-After` header for retry timing guidance.

## FAQ

*   **What does the `status` field mean?**
    Every term is classified into one of four living statuses: `rising` (actively gaining traction), `peak` (at maximum usage), `cringe` (past its prime but still in circulation), and `dead` (no longer in active use). This is the primary differentiator from static slang references — it tells you whether a term is still socially viable, not just what it means.

*   **What does the `over_25_flag` mean?**
    Terms tagged `over_25_flag: true` are slang that reads as inauthentic, forced, or embarrassing when used by speakers over 25. 50 terms in the database carry this flag. It is intended as a practical guide for brand voice decisions and content copy review — not a strict rule.

*   **What do the brand safety ratings mean?**
    The four levels are `safe` (appropriate for all brand contexts), `caution` (fine in youth-oriented contexts but review before broader use), `risky` (likely to alienate or offend some audiences), and `toxic` (inappropriate for brand use in any context). Each term in the database carries exactly one rating.

*   **How often is the data updated?**
    The trending endpoint is updated monthly. The broader term database is curated on an ongoing basis as terms emerge, peak, or die across TikTok, Twitter, Twitch, and other source communities.

*   **What if a term lookup returns a `404`?**
    The database covers 160+ terms but does not claim exhaustive coverage of all slang in circulation. A `404` means the submitted term is not currently in the database. Check the `match_type` field in successful responses — the API may return a fuzzy or partial match for near-miss queries rather than a strict `404`.

*   **How does the translate endpoint work?**
    Submit a plain English word or phrase to `/translate` and the API returns current slang equivalents from its 44-pair translation map. Coverage is limited to the translation pairs in the database; phrases with no matching translation will return an appropriate not-found response rather than a fabricated result.

*   **How do I authenticate my requests?**
    All requests require an `x-api-market-key` header with your API key obtained from RapidAPI.

*   **What is the rate limit?**
    The API enforces a limit of 60 requests per minute across all plans. See the Rate Limits section for handling guidance.

## Contact Us

If you have any questions or need assistance, you can reach out through the embedded chat on the bottom right corner of the page or send an email to 21truescarystories@gmail.com.

Never use dead slang again. Query 160+ real slang terms with living status (rising/peak/cringe/dead), generation association, brand-safety rating, and a "do not