Text to Emoji API Reference

API Overview

Text to Emoji is a simple tool for converting text into emojis. It returns the emojis that represent the given text. To use this API, you need an API key. You can get one by creating a free account and visiting your dashboard.

Important: Ensure that this API is enabled from within your dashboard to use it in your application. If not, you may receive a 403 error

View API in Directory

Client Libaries

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

run in postman button npm logo pypi logo nuget logo

Convert Text to Emoji

1 Token

	
#POST Request
https://api.apiverve.com/v1/texttoemoji	

	
					

x-api-key (required)

This is a required header on every request. Your API Key is found from within your dashboard

accept

This is an optional header. Set the value to application/json, application/xml, or application/yaml


textstring(required)

The text you want converted into emojis


Sample Request
	
import requests

url = "https://api.apiverve.com/v1/texttoemoji"

payload = { "text": "I am so excited to go to the lake and swim" }
headers = {
	"x-api-key": "YOUR_API_KEY",
	"Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)

print(response.json())
	
							
	
using System.Net.Http.Headers;
var client = new HttpClient();
var request = new HttpRequestMessage
{
	Method = HttpMethod.Post,
	RequestUri = new Uri("https://api.apiverve.com/v1/texttoemoji"),
	Headers =
	{
		{ "x-api-key", "YOUR_API_KEY" }
	},
	Content = new StringContent("{ \"text\": \"I am so excited to go to the lake and swim\" }")
	{
		Headers =
		{
			ContentType = new MediaTypeHeaderValue("application/json")
		}
	}
};
using (var response = await client.SendAsync(request))
{
	response.EnsureSuccessStatusCode();
	var body = await response.Content.ReadAsStringAsync();
	Console.WriteLine(body);
}
	
							
	
const data = JSON.stringify({ "text": "I am so excited to go to the lake and swim" });

const xhr = new XMLHttpRequest();
xhr.withCredentials = true;

xhr.addEventListener('readystatechange', function () {
	if (this.readyState === this.DONE) {
		console.log(this.responseText);
	}
});

xhr.open('POST', 'https://api.apiverve.com/v1/texttoemoji');
xhr.setRequestHeader('x-api-key', 'YOUR_API_KEY');
xhr.setRequestHeader('Content-Type', 'application/json');
xhr.setRequestHeader('Accept', 'application/json');

xhr.send(data);
	
							
	
const request = require('request');

const options = {
  method: 'POST',
  url: 'https://api.apiverve.com/v1/texttoemoji',
  headers: {
    'x-api-key': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
    Accept: 'application/json'
  },
  body: { "text": "I am so excited to go to the lake and swim" },
  json: true
};

request(options, function (error, response, body) {
	if (error) throw new Error(error);

	console.log(body);
});
	
							
	
HttpRequest request = HttpRequest.newBuilder()
		.uri(URI.create("https://api.apiverve.com/v1/texttoemoji"))
		.header("x-api-key", "YOUR_API_KEY")
		.header("Content-Type", "application/json")
		.header("Accept", "application/json")
		.method("POST", HttpRequest.BodyPublishers.ofString("{ \"text\": \"I am so excited to go to the lake and swim\" }"))
		.build();
HttpResponse response = HttpClient.newHttpClient().send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());
	
							
	
import Foundation

let headers = [
	"x-api-key": "YOUR_API_KEY",
	"Content-Type": "application/json"
]
let parameters = ["text" : "I am so excited to go to the lake and swim",] as [String : Any]

let postData = JSONSerialization.data(withJSONObject: parameters, options: [])

let request = NSMutableURLRequest(url: NSURL(string: "https://api.apiverve.com/v1/texttoemoji")! as URL,
				cachePolicy: .useProtocolCachePolicy,
                timeoutInterval: 10.0)

request.httpMethod = "POST"
request.allHTTPHeaderFields = headers
request.httpBody = postData as Data

let session = URLSession.shared
let dataTask = session.dataTask(with: request as URLRequest, completionHandler: { (data, response, error) -> Void in
	if (error != nil) {
		print(error as Any)
	} else {
		let httpResponse = response as? HTTPURLResponse
		print(httpResponse)
	}
})

dataTask.resume()
	
							
	
curl --request POST \
	--url https://api.apiverve.com/v1/texttoemoji \
	--header 'Accept: application/json' \
	--header 'Content-Type: application/json' \
	--header 'x-api-key: YOUR_API_KEY' \
	--data '{ "text": "I am so excited to go to the lake and swim" }'
	
							

Sample Response
	
{
  "status": "ok",
  "error": null,
  "data": {
    "emojis": [
      "πŸ‘ˆπŸΎ",
      "βœ¨πŸ‘",
      "πŸ”₯πŸ‘πŸ½",
      "πŸ‘ŠπŸΎπŸ’ͺ🏾",
      "πŸ”₯πŸ€™πŸΌ",
      "🀌🏽πŸ”₯",
      "πŸ€©πŸ‘πŸ»",
      "πŸ˜πŸ“šπŸ™Œ",
      "😞",
      "πŸ‘‰πŸ½πŸ‘ˆπŸ½"
    ]
  },
  "code": 200
}
	
							
	
<Root>
  <status>ok</status>
  <error />
  <data>
    <emojis>👈🏾</emojis>
    <emojis>✨👏</emojis>
    <emojis>🔥👏🏽</emojis>
    <emojis>👊🏾💪🏾</emojis>
    <emojis>🔥🤙🏼</emojis>
    <emojis>🤌🏽🔥</emojis>
    <emojis>🤩👏🏻</emojis>
    <emojis>😁📚🙌</emojis>
    <emojis>😞</emojis>
    <emojis>👉🏽👈🏽</emojis>
  </data>
  <code>200</code>
</Root>
	
							
	
status: ok
error: 
data:
  emojis:
  - "\U0001F448\U0001F3FE"
  - "✨\U0001F44F"
  - "\U0001F525\U0001F44F\U0001F3FD"
  - "\U0001F44A\U0001F3FE\U0001F4AA\U0001F3FE"
  - "\U0001F525\U0001F919\U0001F3FC"
  - "\U0001F90C\U0001F3FD\U0001F525"
  - "\U0001F929\U0001F44F\U0001F3FB"
  - "\U0001F601\U0001F4DA\U0001F64C"
  - "\U0001F61E"
  - "\U0001F449\U0001F3FD\U0001F448\U0001F3FD"
code: 200

	
							
Live Test API in Playground

Response Types

The Text to Emoji API supports the following response content types:

application/json, application/xml, application/yaml

You can specify the response content type by setting the Accept header in your request. If you don't specify a content type, the API will default to application/json.

Authentication

The Text to Emoji API uses an API Key to authenticate requests. You can view and manage your API key by visiting your dashboard.

Your API keys carry many privileges. To keep them from being abused, please do not share the keys on client-side code or Github etc. Keep them very secure.

To use any API, you must have it enabled from within your dashboard. Disabled APIs will fail to respond to your requests.

All requests made to the API must contain the header x-api-key in each of your requests. API requests without authentication will fail.

All API requests must also be made over secure HTTPS. Requests made over plain HTTP will fail.

Error Code Meaning
401 Your request was made with invalid credentials. This error also appears when you don't pass the x-api-key header in your request.
403 Typically, this occurs when you are trying to access an API that you have not enabled.

Rate Limits

	
{
    "status": "error",
    "data": null,
    "error": "tokens have been depleted",
    "code": 429
}
	
							

Each subscription has its own monthly token limit. Your token count is based on your subscription plan. If you reach your limits, don't worry. You can always upgrade or downgrade at any time.

When you reach your limit, the service will stop responding and typically return an HTTP 429 response status code. The error will also contain a detailed JSON.

The Text to Emoji API uses the following error code:

Error Code Meaning
429 You have exceeded your rate limit and further requests will be denied until the next cycle.

Error Codes

For reference, the Text to Emoji API uses the following error codes:

Error Code Meaning
Code Message
200 The request was successful. The response will include the requested data.
400 The request was invalid. The response will include a message that explains the error.
401 The request was not authorized. Usually, this means that the API key is missing or invalid.
403 This means that the request was trying to access a resource that it does not have permission to access.
404 This means that the resource you are trying to access does not exist.
429 This means that you have reached the rate limit. The response will include a Retry-After header that indicates how many seconds you need to wait before making a new request.
500 This means that there was an error on the server side. We are alerted when this happens and we will work to fix it as soon as possible.
ON THIS PAGE