Overview
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.
Live Test Emoji Decorator API →
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl -X POST https://api.apiverve.com/v1/emojidecorator \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"text": "I am so excited to go to the lake and swim"
}'const res = await fetch('https://api.apiverve.com/v1/emojidecorator', {
method: 'POST',
headers: {
'x-api-key': 'your_api_key_here',
'Content-Type': 'application/json',
},
body: JSON.stringify({
"text": "I am so excited to go to the lake and swim"
}),
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.post(
"https://api.apiverve.com/v1/emojidecorator",
headers={"x-api-key": "your_api_key_here"},
json={
"text": "I am so excited to go to the lake and swim"
},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
"strings"
)
func main() {
body := strings.NewReader(`{
"text": "I am so excited to go to the lake and swim"
}`)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/emojidecorator", body)
req.Header.Set("Content-Type", "application/json")
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
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.
Parameters
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
textRequired | string | The text you want decorated with emojis |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"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 |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- 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.
Other ways to use Emoji Decorator
Set up Emoji Decorator on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Text Processing: