Emoji Lookup API GET

Documentation Start for free →

Emoji is a simple tool for getting emoji data. It returns the emoji name, category, and more.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/emoji

Verification

Format

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

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Emoji Lookup response payload
  }
}

About the Emoji Lookup API

Emoji works by retrieving emoji data from a curated database and providing it in a structured format. The emoji database is updated regularly to ensure accurate and up-to-date information.

What people use it for

Emoji Lookup: Use the Emoji API to get emoji data based on the emoji tag. Use the data to retrieve emoji information, display emoji details, and enhance user experience
Emoji Search: Search for emoji data by using the Emoji API based on the category or tag. Use the data to find specific emoji, filter emoji results, and improve emoji search
Emoji Conversion: Convert emoji to text by using the Emoji API. Use the data to translate emoji characters, display emoji names, and enhance text readability
Emoji Analysis: Analyze emoji data by using the Emoji API to study emoji patterns, sentiment analysis, and text classification. Use the data to explore emoji meanings, usage trends, and cultural significance

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 Emoji Lookup

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 Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Emoji Lookup API.

Read the docs →

What does the Emoji Lookup API do?

Emoji is a simple tool for getting emoji data. It returns the emoji name, category, and more.

How do I authenticate Emoji Lookup API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Emoji Lookup API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Emoji Lookup API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Emoji Lookup API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Emoji Lookup API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/emoji

Sent in the query string. 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
`emoji`Required	string	`🥳`	The emoji for which you want to get the text representation (e.g., 🥳)

Example request

1
2

curl "https://api.apiverve.com/v1/emoji?emoji=%F0%9F%A5%B3" \
  -H "x-api-key: YOUR_API_KEY"

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.

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 — GET /v1/emoji

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": {
    "count": 1,
    "emojisFound": [
      {
        "emoji": "🥳",
        "description": "partying face",
        "category": "Smileys & Emotion",
        "aliases": [
          "partying_face"
        ],
        "tags": [
          "celebration",
          "birthday"
        ],
        "unicode_version": "11.0",
        "ios_version": "12.1",
        "codePoint": "1f973"
      }
    ]
  }
}

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
`count`	number	`1`	Number of emoji results found in response
`emojisFound`	array[1]		Array of emoji objects with detailed information
`emoji`	string	`"🥳"`	The emoji character symbol
`description`	string	`"partying face"`	Human-readable description of the emoji
`category`	string	`"Smileys & Emotion"`	Emoji category classification for organization
`aliases`Premium	array	`[partying_face]`	Alternative names for the emoji
`tags`Premium	array	`[celebration, ...]`	Tags describing emoji meaning and usage
`unicode_version`Premium	string	`"11.0"`	Unicode standard version where emoji was introduced
`ios_version`Premium	string	`"12.1"`	iOS version when emoji was first supported
`codePoint`Premium	string	`"1f973"`	Hexadecimal Unicode code point value

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 Lookup 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 — GET /v1/emoji

No SDK to install — this is a plain HTTPS call to /v1/emoji 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/emoji" \
  -H "x-api-key: YOUR_API_KEY"

Resources

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

Also published for

@apiverve/emojinpm apiverve-emojiPyPI APIVerve.API.EmojiLookupNuGet

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

Call it from Node.js — GET /v1/emoji

Install the Node.js SDK, then call the Emoji Lookup 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/emoji

Node.js

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

Resources

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

Also published for

apiverve-emojiPyPI APIVerve.API.EmojiLookupNuGet

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

Call it from Python — GET /v1/emoji

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

Install — PyPI

pip install apiverve-emoji

Python

import requests

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

Resources

PyPIapiverve-emojiThe published Python client, versioned and signed.GitHubapiverve/emoji-apiSource, issues and the examples this page is built from.ReferenceEmoji Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/emojinpm APIVerve.API.EmojiLookupNuGet

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

Call it from C# / .NET — GET /v1/emoji

Install the C# / .NET SDK, then call the Emoji Lookup 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.EmojiLookup

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/emoji");
Console.WriteLine(json);

Resources

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

Also published for

@apiverve/emojinpm apiverve-emojiPyPI

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

Call it from Go — GET /v1/emoji

No SDK to install — this is a plain HTTPS call to /v1/emoji 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/emoji", 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/emojinpm apiverve-emojiPyPI APIVerve.API.EmojiLookupNuGet

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

Call it from PHP — GET /v1/emoji

No SDK to install — this is a plain HTTPS call to /v1/emoji 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/emoji");
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/emojinpm apiverve-emojiPyPI APIVerve.API.EmojiLookupNuGet

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

Call it from Ruby — GET /v1/emoji

No SDK to install — this is a plain HTTPS call to /v1/emoji 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/emoji")
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/emojinpm apiverve-emojiPyPI APIVerve.API.EmojiLookupNuGet

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

All articles →

The Timezone Bug That Cost Us a ClientA scheduled email went out at 3 AM instead of 9 AM. The client wasn't happy. Here's what went wrong.Read

Build a Lead Enrichment Pipeline That Actually WorksTurn email addresses into full customer profiles. Location, company, social links—automatically. Here's how to build it.Read

Weather APIs: Build a Dashboard That's Actually UsefulCurrent conditions, forecasts, air quality, sunrise times—here's how to build a weather dashboard users will love.Read

Emoji Lookup API GET

Try it — live request, no key required

About the Emoji Lookup API

What people use it for

Ways to call it

Other ways to use Emoji Lookup

Questions.

Request parameters — GET /v1/emoji

Required

Authentication

Response — GET /v1/emoji

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/emoji

Resources

Also published for

Call it from Node.js — GET /v1/emoji

Resources

Also published for

Call it from Python — GET /v1/emoji

Resources

Also published for

Call it from C# / .NET — GET /v1/emoji

Resources

Also published for

Call it from Go — GET /v1/emoji

Resources

Also published for

Call it from PHP — GET /v1/emoji

Resources

Also published for

Call it from Ruby — GET /v1/emoji

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Emoji Lookup API

Data Lookup

Related articles

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

Explore the catalog