Emoji Lookup

Token Usage:1 per call

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

This API provides reliable and fast access to emoji lookup data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.

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

View API in Directory

Endpoint

GET Request

GET https://api.apiverve.com/v1/emoji

Code Examples

Here are examples of how to call this API in different programming languages:

cURL Request

curl -X GET \
  "https://api.apiverve.com/v1/emoji?emoji=🥳" \
  -H "X-API-Key: your_api_key_here"

JavaScript (Fetch API)

const response = await fetch('https://api.apiverve.com/v1/emoji', {
  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/emoji', headers=headers)

data = response.json()
print(data)

Node.js (Native HTTPS)

const https = require('https');
const url = require('url');

const options = {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
};

const req = https.request('https://api.apiverve.com/v1/emoji', options, (res) => {
  let data = '';
  res.on('data', (chunk) => data += chunk);
  res.on('end', () => console.log(JSON.parse(data)));
});

req.end();

PHP (cURL)

<?php

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/emoji');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'GET');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'X-API-Key: your_api_key_here',
    'Content-Type: application/json'
]);

$response = curl_exec($ch);
curl_close($ch);

$data = json_decode($response, true);
print_r($data);

?>

Go (net/http)

package main

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

)

func main() {
    req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/emoji", 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))
}

Ruby (Net::HTTP)

require 'net/http'
require 'json'

uri = URI('https://api.apiverve.com/v1/emoji')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true

request = Net::HTTP::Get.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'

response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))

Authentication

This API requires authentication via API key. Include your API key in the request header:

Required Header

X-API-Key: your_api_key_here

Parameters

The following parameters are available for this API endpoint:

Parameter	Type	Required	Location	Description	Example
emoji	string	Yes	query	The emoji for which you want to get the text representation (e.g., 🥳)	🥳

Response

The API returns responses in JSON, XML, and YAML formats:

Example Responses

JSON Response

200 OK

{
  "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"
      }
    ]
  }
}

XML Response

200 OK

<Root>
  <status>ok</status>
  <error />
  <data>
    <count>1</count>
    <emojisFound>
      <emoji>🥳</emoji>
      <description>partying face</description>
      <category>Smileys &amp; Emotion</category>
      <aliases>partying_face</aliases>
      <tags>celebration</tags>
      <tags>birthday</tags>
      <unicode_version>11.0</unicode_version>
      <ios_version>12.1</ios_version>
      <codePoint>1f973</codePoint>
    </emojisFound>
  </data>
</Root>

YAML Response

200 OK

status: ok
error: 
data:
  count: 1
  emojisFound:
  - emoji: "\U0001F973"
    description: partying face
    category: Smileys & Emotion
    aliases:
    - partying_face
    tags:
    - celebration
    - birthday
    unicode_version: 11.0
    ios_version: 12.1
    codePoint: 1f973

Live Test API in Playground

Response Structure

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

Field	Type	Description	Example
status	string	Indicates whether the request was successful ("ok") or failed ("error")	ok
error	string \| null	Contains error message if status is "error", otherwise null	null
data	object \| null	Contains the API response data if successful, otherwise null	{...}

Response Data Fields

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

Field	Type	Sample Value
count	number	1
emojisFound	array	[{"emoji":"🥳","description":"partying face","category":"Smileys & Emotion","aliases":["partying_face"],"tags":["celebration","birthday"],"unicode_version":"11.0","ios_version":"12.1","codePoint":"1f973"}]

Headers

Required and optional headers for API requests:

Header Name	Required	Example Value	Description
X-API-Key	Yes	your_api_key_here	Your APIVerve API key. Found in your dashboard under API Keys.
Accept	No	application/json	Specify response format: application/json (default), application/xml, or application/yaml
User-Agent	No	MyApp/1.0	Identifies your application for analytics and debugging purposes
X-Request-ID	No	req_123456789	Custom request identifier for tracking and debugging requests
Cache-Control	No	no-cache	Control caching behavior for the request and response

Client Libraries

To get started with minimal code, most of our APIs are available through client libraries and clients:

Error Codes

The API uses standard HTTP status codes to indicate success or failure:

Status Code	Message	Description
200	OK	Request successful, data returned
400	Bad Request	Invalid request parameters or malformed request
401	Unauthorized	Missing or invalid API key
403	Forbidden	API key does not have permission for this endpoint
429	Too Many Requests	Rate limit exceeded, please slow down requests
500	Internal Server Error	Server error, please try again later

What's Next?

Continue your journey with these recommended resources

Browse All APIs

Explore our complete catalog of APIs

Authentication Guide

Learn about API keys and security

Rate Limits

Understand usage limits and best practices

Was this page helpful?

Help us improve our documentation