Unicode Character LookupUnicode Character Lookup API

OnlineCredit Usage:1 per callRefreshed 1 month ago
avg: 177ms|p50: 171ms|p75: 181ms|p90: 194ms|p99: 219ms

Overview

To use Unicode Character Lookup, you need an API key. You can get one by creating a free account and visiting your dashboard.

GET Endpoint

URL
https://api.apiverve.com/v1/unicodelookup

Example

How to call the Unicode Character Lookup API in different programming languages.

cURL Request
curl -X GET \
  "https://api.apiverve.com/v1/unicodelookup?character=%F0%9F%91%8B&codepoint=1F44B" \
  -H "X-API-Key: your_api_key_here"
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/unicodelookup?character=%F0%9F%91%8B&codepoint=1F44B', {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

response = requests.get('https://api.apiverve.com/v1/unicodelookup?character=%F0%9F%91%8B&codepoint=1F44B', headers=headers)

data = response.json()
print(data)
Go (net/http)
package main

import (
    "fmt"
    "io"
    "net/http"

)

func main() {
    req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/unicodelookup?character=%F0%9F%91%8B&codepoint=1F44B", nil)

    req.Header.Set("X-API-Key", "your_api_key_here")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}
Example Response
{
  "status": "ok",
  "error": null,
  "data": {
    "character": "�",
    "codepoint": "U+D83D",
    "decimal": 55357,
    "hex": "D83D",
    "utf16": "\\uD83D",
    "category": "Control",
    "name": null
  }
}

Authentication

The Unicode Character Lookup API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the Unicode Character Lookup API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the Unicode Character Lookup API:

Lookup Character

ParameterTypeRequiredDescriptionDefaultExample
characterstringrequired
The Unicode character to lookup
-👋
codepointstringoptional
The Unicode codepoint in hex (e.g., '1F44B' or 'U+1F44B')
-1F44B

Response

The Unicode Character Lookup API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.

Other Response Formats

XML Response
200 OK
<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <character>�</character>
    <codepoint>U+D83D</codepoint>
    <decimal>55357</decimal>
    <hex>D83D</hex>
    <utf16>\uD83D</utf16>
    <category>Control</category>
    <name xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  </data>
</response>
YAML Response
200 OK
status: ok
error: null
data:
  character: �
  codepoint: U+D83D
  decimal: 55357
  hex: D83D
  utf16: \uD83D
  category: Control
  name: null
CSV Response
200 OK
keyvalue
character�
codepointU+D83D
decimal55357
hexD83D
utf16\uD83D
categoryControl
name

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains the API response data if successful, otherwise null{...}

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

FieldTypeSample ValueDescription
characterstring"�"
The Unicode character being looked up
codepointstring"U+D83D"
The Unicode codepoint in U+ notation format
decimalnumber55357
The decimal representation of the character codepoint
hexstring"D83D"
The hexadecimal representation of the character codepoint
utf16string"\uD83D"
The UTF-16 encoding representation of the character
categorystring"Control"
Unicode category classification (e.g., Control, Letter, Number)
nameobjectnull
The official Unicode name or emoji name for the character

Headers

Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →

GraphQL AccessALPHA

Access Unicode Character Lookup through GraphQL to combine it with other API calls in a single request. Query only the unicode character lookup data you need with precise field selection, and orchestrate complex data fetching workflows.

Test Unicode Character Lookup in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  unicodelookup(
    input: {
      character: "👋"
      codepoint: "1F44B"
    }
  ) {
    character
    codepoint
    decimal
    hex
    utf16
    category
    name
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The Unicode Character Lookup API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →

Rate Limiting

Unicode Character Lookup requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →

Error Codes

The Unicode Character Lookup API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →

SDKs for Unicode Character Lookup

Official Unicode Character Lookup packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

No-Code Integrations

Unicode Character Lookup works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Frequently Asked Questions

How do I get an API key for Unicode Character Lookup?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for Unicode Character Lookup and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does Unicode Character Lookup cost?

Each successful Unicode Character Lookup API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful unicode character lookup lookups.

Can I use Unicode Character Lookup in production?

The free plan is for testing and development only. For production use of Unicode Character Lookup, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.

Can I use Unicode Character Lookup from a browser?
Yes! The Unicode Character Lookup API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
What happens if I exceed my Unicode Character Lookup credit limit?

When you reach your monthly credit limit, Unicode Character Lookup API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?