Enhance plain text with contextually relevant emojis.
Emoji Decorator inserts relevant emojis into plain text strings. Submit any sentence or passage to receive the complete string decorated with fitting emojis.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"decorated": "I am so excited 🥂 to go 😄🙌🏽 to the lake 🤘🏻🇺🇸 and swim 🏊"
}
}
About the Emoji Decorator API
An emoji decorator API that adds emojis to text automatically. Send a raw string of text in the request body and the service picks out the key phrases in your copy and inserts matching emojis after them, returning a decorated string ready for display or publishing.
It is a quick way to make notifications, chat replies, social captions and push messages feel more casual without hand-picking emojis for every line. "I am so excited to go to the lake and swim" comes back with emojis placed after phrases like "excited" and "swim". Because the original words are left untouched and only emojis are added, you can drop the result straight into an existing template.
The response has a single field, the decorated text, and it is the same on every plan, including the Free plan. Emoji choice includes a random element, so the same sentence can come back with different emojis on repeated calls, which keeps automated messages from looking identical.
How it works
Emoji Decorator uses the open-source emoji-whisperer package. Your text is first split into keyword phrases with a RAKE-style pass: the text is broken on spaces, and runs of words between common stopwords become candidate phrases, each scored by how its words co-occur. The service calls the decorator with full density, so every extracted phrase is considered rather than only the top-scoring few.
For each phrase, the package lowercases and stems the words, ignores URLs and hashtags, and looks them up in a bundled index that maps words to emoji groups, scoring the matching emoji groups and keeping the five highest-scoring ones. One of those five is picked at random and inserted after the first occurrence of that phrase in the text, separated by a space. A candidate can be a single emoji or a short sequence, which is why some insertions in decorated contain two or three emojis together. Phrases with no match in the index are left without an emoji.
The result is that decorated always contains your original text in its original order, with emojis added after matched phrases. Nothing is removed or rewritten, and punctuation stays where it was. Because selection is random, output is not deterministic: cache the result if you need the same decoration twice. Matching is word-based and English-oriented; there is no sentiment model or AI call involved, so text in other languages or made of rare words may come back with few or no emojis. The response is identical on every plan.
What people use it for
- Social Media Scheduling
- Queue drafts for automated publishing with contextual emojis inserted across captions and promotional posts.
- Push Notification Copy
- Product marketers can spruce up mobile app push notifications to boost click-through rates on feature announcements.
- Chatbot Response Styling
- To make automated support bots sound friendlier, process outbound conversational answers before delivering them to customers.
- Email Subject Formatting
- When sending out marketing newsletters, format subject lines and preview text with relevant icons automatically.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Emoji Decorator
Same data, same APIVerve account, same credit balance — one key works on all of them.
Where does the API place emojis in the text?
Does the API replace words with emojis or keep the text intact?
Does the response return the decorated text or an emoji list?
Can I send full sentences and paragraphs to the endpoint?
Which plan fits decorating 20,000 messages a month?
Request parameters — POST /v1/emojidecorator
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
textRequired | string | hello world | The text you want decorated with emojis |
curl -X POST "https://api.apiverve.com/v1/emojidecorator" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"I am so excited to go to the lake and swim"}'Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
content-typeRequired | POST body | application/json |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — POST /v1/emojidecorator
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"decorated": "I am so excited 🥂 to go 😄🙌🏽 to the lake 🤘🏻🇺🇸 and swim 🏊"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
decorated | string | "I am so excited 🥂 to go 😄🙌🏽 to the lake 🤘🏻🇺🇸 and swim 🏊" | Input text enhanced with contextually relevant emojis throughout |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Emoji Decorator calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — POST /v1/emojidecorator
No SDK to install — this is a plain HTTPS call to /v1/emojidecorator with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/emojidecorator" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — POST /v1/emojidecorator
Install the Node.js SDK, then call the Emoji Decorator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/emojidecoratorconst res = await fetch("https://api.apiverve.com/v1/emojidecorator", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — POST /v1/emojidecorator
No SDK to install — this is a plain HTTPS call to /v1/emojidecorator with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/emojidecorator",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — POST /v1/emojidecorator
Install the C# / .NET SDK, then call the Emoji Decorator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.EmojiDecoratorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/emojidecorator");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — POST /v1/emojidecorator
No SDK to install — this is a plain HTTPS call to /v1/emojidecorator with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/emojidecorator", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — POST /v1/emojidecorator
No SDK to install — this is a plain HTTPS call to /v1/emojidecorator with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/emojidecorator");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — POST /v1/emojidecorator
No SDK to install — this is a plain HTTPS call to /v1/emojidecorator with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/emojidecorator")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Emoji Decorator form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Emoji Decorator API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Emoji Decorator API.
Text Processing
- Acronym Expander
- Anagram Detector
- Antonym Finder
- Cron Expression Parser
- Data Masking
- Did You Mean
- Emoji Decorator
- Gibberish Detector
- Grammar Check
- ISBN Validator
- JSON Schema Validator
- Keyword Extractor
- Leet Speak
- Levenshtein Distance
- Line Sorter
- Markdown Link Extractor
- Palindrome Checker
- Parts Of Speech
- Phonetic Encoder
- Pig Latin
- Profanity Filter
- Reading Time Calculator
- Regex Tester
- Remove Punctuation
- Reverse Text
- Rhyming Words
- Slugify
- Spell Checker
- Syllable Counter
- Tax ID Validator
- Tense Converter
- Text Language
- Text Lemmatizer
- Text Readability Score
- Text Similarity
- Text Styler
- Text Summarizer
- Text to Emoji
- Title Case Converter
- Translator
- Vowel Counter
- Website Readability
- Word Lexicon Analyzer
- Word Opposites
- Word Pronunciation
Related articles
All articles →
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read
Summarize Text with AI: A Practical GuideUse AI to summarize articles, documents, and user content. Tutorial with code for content platforms, research tools, and dashboards.Read
7 Content Moderation Mistakes That Sink AppsYour app allows user content. Here are the moderation mistakes that get apps pulled from stores.Read