Identify the codepoint, category, and name behind any character.
Unicode Character Lookup inspects any character or hex codepoint to find its decimal value, hex notation, and UTF-16 encoding. The response also identifies the character category and supplies names for emoji.
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": {
"character": "�",
"codepoint": "U+D83D",
"decimal": 55357,
"hex": "D83D",
"utf16": "\\uD83D",
"category": "Control",
"name": null
}
}
About the Unicode Character Lookup API
Unicode Character Lookup works by analyzing Unicode characters or codepoints to retrieve detailed information including decimal/hex codepoint, UTF-16 encoding, category (letter, number, emoji, etc.), and emoji names from the Unicode emoji database.
What people use it for
- Character Analysis
- Analyze Unicode characters in text to understand their encoding, category, and properties
- Emoji Information
- Look up emoji names and Unicode information for emoji keyboards, pickers, or documentation
- Debugging
- Debug character encoding issues by examining Unicode properties and encodings of problematic characters
- Documentation
- Generate documentation about supported characters, emojis, or special symbols with detailed Unicode info
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 Unicode Character Lookup
Same data, same APIVerve account, same credit balance — one key works on all of them.
Does it return details for emoji as well as standard letters and symbols?
Can I look up a character by its hex codepoint instead of passing the symbol?
What would 20,000 character lookups a month cost me?
Where does the character and emoji metadata come from?
Can I display the returned Unicode data inside my own software?
Request parameters — GET /v1/unicodelookup
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.
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
characterOptional | string | 👋 | The Unicode character to lookup. Supply either character or codepoint. |
codepointOptional | string | 1F44B | The Unicode codepoint in hex (e.g., '1F44B' or 'U+1F44B'). Supply either character or codepoint. |
curl "https://api.apiverve.com/v1/unicodelookup?character=%F0%9F%91%8B&codepoint=1F44B" \
-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-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. |
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/unicodelookup
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": {
"character": "�",
"codepoint": "U+D83D",
"decimal": 55357,
"hex": "D83D",
"utf16": "\\uD83D",
"category": "Control",
"name": null
}
}
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 |
|---|---|---|---|
character | string | "�" | The Unicode character being looked up |
codepoint | string | "U+D83D" | The Unicode codepoint in U+ notation format |
decimal | number | 55357 | The decimal representation of the character codepoint |
hex | string | "D83D" | The hexadecimal representation of the character codepoint |
utf16 | string | "\uD83D" | The UTF-16 encoding representation of the character |
category | string | "Control" | Unicode category classification (e.g., Control, Letter, Number) |
name | object | null | The emoji name when the character is an emoji (e.g. "red heart"); null for other characters |
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 | Unicode Character 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.
Call it from cURL — GET /v1/unicodelookup
No SDK to install — this is a plain HTTPS call to /v1/unicodelookup 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/unicodelookup" \
-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 — GET /v1/unicodelookup
Install the Node.js SDK, then call the Unicode Character Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/unicodelookupconst res = await fetch("https://api.apiverve.com/v1/unicodelookup", {
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 — GET /v1/unicodelookup
No SDK to install — this is a plain HTTPS call to /v1/unicodelookup 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/unicodelookup",
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 — GET /v1/unicodelookup
Install the C# / .NET SDK, then call the Unicode Character Lookup 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.UnicodeCharacterLookupusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/unicodelookup");
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 — GET /v1/unicodelookup
No SDK to install — this is a plain HTTPS call to /v1/unicodelookup 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/unicodelookup", 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 — GET /v1/unicodelookup
No SDK to install — this is a plain HTTPS call to /v1/unicodelookup 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/unicodelookup");
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 — GET /v1/unicodelookup
No SDK to install — this is a plain HTTPS call to /v1/unicodelookup 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/unicodelookup")
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 Unicode Character Lookup 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 — Unicode Character Lookup 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 Unicode Character Lookup API.
Data Lookup
- ASN Lookup
- Bible
- Country Calling Code
- Dictionary
- Dog Breeds
- Emoji Lookup
- Gender Detector
- Gravatar Lookup
- IP Demographics
- Lottery Numbers
- Nobel Prizes
- Open Source Licenses
- Thesaurus
- Timezone Lookup
- Unicode Character Lookup
- World Time
- ZIP Demographics
Related articles
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