Text to Emoji API

POST

Translate words and phrases into matching emojis.

Text to Emoji converts plain text strings into matching emoji representations. Send any word or phrase and receive the corresponding emoji characters.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/texttoemoji

Body

textstring

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "emojis": [
      "👈🏾",
      "✨👏",
      "🔥👏🏽",
      "👊🏾💪🏾",
      "🔥🤙🏼",
      "🤌🏽🔥",
      "🤩👏🏻",
      "😁📚🙌",
      "😞",
      "👉🏽👈🏽"
    ]
  }
}

About the Text to Emoji API

Submit a text string in the POST request body. The service processes the input to identify words and phrases, mapping them directly to their corresponding emoji characters. The response delivers the resulting emoji string in the emojis field.

What people use it for

Chat Message Reactions: Chat applications can suggest relevant reaction icons by converting user message drafts into matching emoji before sending.
Social Feed Captioning: When publishing automated marketing posts, schedule services convert keyword phrases into emoji to draw visual attention in feeds.
Vocabulary Learning Drills: Educational software transforms vocabulary terms into pictograms for early-stage language drills and symbol association quizzes.
Push Notification Badges: Decorate push notifications by turning event status updates into quick visual icon summaries for mobile lock screens.

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

View all integrations →

Other ways to use Text to Emoji

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets

Questions.

Common questions about the Text to Emoji API.

Read the docs →

Can I convert full sentences or only single words?

You can submit full sentences, multi-word phrases, or individual words. Text to Emoji evaluates the string provided in the text parameter and returns the emojis that represent it.

Does the response return only emojis or the original text mixed in?

The response returns only the emoji representation of your submitted text in the emojis field. It gives you the emojis matched to your text rather than echoing the original message with emojis inserted.

Does each request convert a single string at a time?

Yes. Each POST request accepts one text parameter. To convert multiple distinct messages or sentences independently, send each as its own request.

Which plan fits 50,000 text conversions a month?

The Starter plan easily covers this volume. Each conversion uses 2 credits, so 50,000 calls consume 100,000 of the 200,000 monthly credits included on Starter. That volume works out to about $0.30 per 1,000 calls. The Free plan provides 100 calls per month for testing.

Can I use this to generate emoji suggestions for user messages?

Yes. You can pass chat messages, search queries, or user status text into the text parameter to generate relevant emoji matches. It works well for chat reactions, message decoration, or quick emoji autocomplete features.

Request parameters — POST /v1/texttoemoji

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
`text`Required	string	`hello world`	The text you want converted into emojis

Example request

curl -X POST "https://api.apiverve.com/v1/texttoemoji" \
  -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-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.
`content-type`Required	POST body	`application/json`

401 is the only auth verdict

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/texttoemoji

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.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "emojis": [
      "👈🏾",
      "✨👏",
      "🔥👏🏽",
      "👊🏾💪🏾",
      "🔥🤙🏼",
      "🤌🏽🔥",
      "🤩👏🏻",
      "😁📚🙌",
      "😞",
      "👉🏽👈🏽"
    ]
  }
}

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
`emojis`	array	`[👈🏾, ...]`	Emoji renderings of the input text, one string per suggested variation

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	Text to Emoji 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.

Compare all pricing tiers →

Call it from cURL — POST /v1/texttoemoji

No SDK to install — this is a plain HTTPS call to /v1/texttoemoji with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/texttoemoji" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/texttoemoji-apiSource, issues and the examples this page is built from.ReferenceText to Emoji API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/texttoemojinpm APIVerve.API.TexttoEmojiNuGet

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/texttoemoji

Install the Node.js SDK, then call the Text to Emoji API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/texttoemoji

Node.js

const res = await fetch("https://api.apiverve.com/v1/texttoemoji", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/texttoemojiThe published Node.js client, versioned and signed.GitHubapiverve/texttoemoji-apiSource, issues and the examples this page is built from.ReferenceText to Emoji API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.TexttoEmojiNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — POST /v1/texttoemoji

No SDK to install — this is a plain HTTPS call to /v1/texttoemoji with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/texttoemoji",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/texttoemojinpm APIVerve.API.TexttoEmojiNuGet

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/texttoemoji

Install the C# / .NET SDK, then call the Text to Emoji API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.TexttoEmoji

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/texttoemoji");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.TexttoEmojiThe published C# / .NET client, versioned and signed.GitHubapiverve/texttoemoji-apiSource, issues and the examples this page is built from.ReferenceText to Emoji API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/texttoemojinpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — POST /v1/texttoemoji

No SDK to install — this is a plain HTTPS call to /v1/texttoemoji 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/texttoemoji", 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

@apiverve/texttoemojinpm APIVerve.API.TexttoEmojiNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — POST /v1/texttoemoji

No SDK to install — this is a plain HTTPS call to /v1/texttoemoji with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/texttoemoji");
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

@apiverve/texttoemojinpm APIVerve.API.TexttoEmojiNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — POST /v1/texttoemoji

No SDK to install — this is a plain HTTPS call to /v1/texttoemoji with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/texttoemoji")
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.body

Resources

Also published for

@apiverve/texttoemojinpm APIVerve.API.TexttoEmojiNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Text Processing

View all 45 →

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

Text to Emoji API

Try it — live request, no key required

About the Text to Emoji API

What people use it for

Ways to call it

Other ways to use Text to Emoji

Questions.

Request parameters — POST /v1/texttoemoji

Required

Authentication

Response — POST /v1/texttoemoji

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — POST /v1/texttoemoji

Resources

Also published for

Call it from Node.js — POST /v1/texttoemoji

Resources

Also published for

Call it from Python — POST /v1/texttoemoji

Resources

Also published for

Call it from C# / .NET — POST /v1/texttoemoji

Resources

Also published for

Call it from Go — POST /v1/texttoemoji

Resources

Also published for

Call it from PHP — POST /v1/texttoemoji

Resources

Also published for

Call it from Ruby — POST /v1/texttoemoji

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Text to Emoji API

Text Processing

Related articles

Ready to build with Text to Emoji? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog