Unicode Escape/Unescape API
Unicode Escape/Unescape is a tool for converting characters to Unicode escape sequences and vice versa. It handles all Unicode characters including emojis and surrogate pairs.
The Unicode Escape/Unescape API provides reliable and fast access to unicode escape/unescape data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.
To use Unicode Escape/Unescape, you need an API key. You can get one by creating a free account and visiting your dashboard.
POST Endpoint
https://api.apiverve.com/v1/unicodeescapeCode Examples
Here are examples of how to call the Unicode Escape/Unescape API in different programming languages:
curl -X POST \
"https://api.apiverve.com/v1/unicodeescape" \
-H "X-API-Key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"text": "Hello World",
"action": "escape"
}'const response = await fetch('https://api.apiverve.com/v1/unicodeescape', {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
},
body: JSON.stringify({
"text": "Hello World",
"action": "escape"
})
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
payload = {
"text": "Hello World",
"action": "escape"
}
response = requests.post('https://api.apiverve.com/v1/unicodeescape', headers=headers, json=payload)
data = response.json()
print(data)const https = require('https');
const url = require('url');
const options = {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
};
const postData = JSON.stringify({
"text": "Hello World",
"action": "escape"
});
const req = https.request('https://api.apiverve.com/v1/unicodeescape', options, (res) => {
let data = '';
res.on('data', (chunk) => data += chunk);
res.on('end', () => console.log(JSON.parse(data)));
});
req.write(postData);
req.end();<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/unicodeescape');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'POST');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
'X-API-Key: your_api_key_here',
'Content-Type: application/json'
]);
curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode({
'text': 'Hello World',
'action': 'escape'
}));
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);
?>package main
import (
"fmt"
"io"
"net/http"
"bytes"
"encoding/json"
)
func main() {
payload := map[string]interface{}{
"text": "Hello World",
"action": "escape"
}
jsonPayload, _ := json.Marshal(payload)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/unicodeescape", bytes.NewBuffer(jsonPayload))
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))
}require 'net/http'
require 'json'
uri = URI('https://api.apiverve.com/v1/unicodeescape')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
payload = {
"text": "Hello World",
"action": "escape"
}
request = Net::HTTP::Post.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'
request.body = payload.to_json
response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;
class Program
{
static async Task Main(string[] args)
{
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");
var jsonContent = @"{
""text"": ""Hello World"",
""action"": ""escape""
}";
var content = new StringContent(jsonContent, Encoding.UTF8, "application/json");
var response = await client.PostAsync("https://api.apiverve.com/v1/unicodeescape", content);
response.EnsureSuccessStatusCode();
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);
}
}Authentication
The Unicode Escape/Unescape API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Unicode Escape/Unescape API directly in your browser with live requests and responses.
Parameters
The Unicode Escape/Unescape API supports multiple query options. Use one of the following:
Option 1: Escape Unicode
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
text | string | required | The text to escape | - | |
action | string | optional | The action to perform Supported values: escapeunescape |
Option 2: Unescape Unicode
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
text | string | required | The Unicode escape sequences to unescape | - | |
action | string | optional | The action to perform Supported values: escapeunescape |
Response
The Unicode Escape/Unescape API returns responses in JSON, XML, YAML, and CSV formats:
Example Responses
{
"status": "ok",
"error": null,
"data": {
"action": "escape",
"original": "Hello World",
"escaped": "\\u0048\\u0065\\u006C\\u006C\\u006F\\u0020\\u0057\\u006F\\u0072\\u006C\\u0064",
"character_count": 11,
"unicode_points": [
{
"char": "H",
"unicode": "\\u0048",
"codepoint": "U+0048"
},
{
"char": "e",
"unicode": "\\u0065",
"codepoint": "U+0065"
},
{
"char": "l",
"unicode": "\\u006C",
"codepoint": "U+006C"
},
{
"char": "l",
"unicode": "\\u006C",
"codepoint": "U+006C"
},
{
"char": "o",
"unicode": "\\u006F",
"codepoint": "U+006F"
},
{
"char": " ",
"unicode": "\\u0020",
"codepoint": "U+0020"
},
{
"char": "W",
"unicode": "\\u0057",
"codepoint": "U+0057"
},
{
"char": "o",
"unicode": "\\u006F",
"codepoint": "U+006F"
},
{
"char": "r",
"unicode": "\\u0072",
"codepoint": "U+0072"
},
{
"char": "l",
"unicode": "\\u006C",
"codepoint": "U+006C"
},
{
"char": "d",
"unicode": "\\u0064",
"codepoint": "U+0064"
}
]
}
}<?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>
<action>escape</action>
<original>Hello World</original>
<escaped>\u0048\u0065\u006C\u006C\u006F\u0020\u0057\u006F\u0072\u006C\u0064</escaped>
<character_count>11</character_count>
<unicode_points>
<unicode_point>
<char>H</char>
<unicode>\u0048</unicode>
<codepoint>U+0048</codepoint>
</unicode_point>
<unicode_point>
<char>e</char>
<unicode>\u0065</unicode>
<codepoint>U+0065</codepoint>
</unicode_point>
<unicode_point>
<char>l</char>
<unicode>\u006C</unicode>
<codepoint>U+006C</codepoint>
</unicode_point>
<unicode_point>
<char>l</char>
<unicode>\u006C</unicode>
<codepoint>U+006C</codepoint>
</unicode_point>
<unicode_point>
<char>o</char>
<unicode>\u006F</unicode>
<codepoint>U+006F</codepoint>
</unicode_point>
<unicode_point>
<char> </char>
<unicode>\u0020</unicode>
<codepoint>U+0020</codepoint>
</unicode_point>
<unicode_point>
<char>W</char>
<unicode>\u0057</unicode>
<codepoint>U+0057</codepoint>
</unicode_point>
<unicode_point>
<char>o</char>
<unicode>\u006F</unicode>
<codepoint>U+006F</codepoint>
</unicode_point>
<unicode_point>
<char>r</char>
<unicode>\u0072</unicode>
<codepoint>U+0072</codepoint>
</unicode_point>
<unicode_point>
<char>l</char>
<unicode>\u006C</unicode>
<codepoint>U+006C</codepoint>
</unicode_point>
<unicode_point>
<char>d</char>
<unicode>\u0064</unicode>
<codepoint>U+0064</codepoint>
</unicode_point>
</unicode_points>
</data>
</response>
status: ok
error: null
data:
action: escape
original: Hello World
escaped: \u0048\u0065\u006C\u006C\u006F\u0020\u0057\u006F\u0072\u006C\u0064
character_count: 11
unicode_points:
- char: H
unicode: \u0048
codepoint: U+0048
- char: e
unicode: \u0065
codepoint: U+0065
- char: l
unicode: \u006C
codepoint: U+006C
- char: l
unicode: \u006C
codepoint: U+006C
- char: o
unicode: \u006F
codepoint: U+006F
- char: ' '
unicode: \u0020
codepoint: U+0020
- char: W
unicode: \u0057
codepoint: U+0057
- char: o
unicode: \u006F
codepoint: U+006F
- char: r
unicode: \u0072
codepoint: U+0072
- char: l
unicode: \u006C
codepoint: U+006C
- char: d
unicode: \u0064
codepoint: U+0064
| key | value |
|---|---|
| action | escape |
| original | Hello World |
| escaped | \u0048\u0065\u006C\u006C\u006F\u0020\u0057\u006F\u0072\u006C\u0064 |
| character_count | 11 |
| unicode_points | [{char:H,unicode:\\u0048,codepoint:U+0048},{char:e,unicode:\\u0065,codepoint:U+0065},{char:l,unicode:\\u006C,codepoint:U+006C},{char:l,unicode:\\u006C,codepoint:U+006C},{char:o,unicode:\\u006F,codepoint:U+006F},{char: ,unicode:\\u0020,codepoint:U+0020},{char:W,unicode:\\u0057,codepoint:U+0057},{char:o,unicode:\\u006F,codepoint:U+006F},{char:r,unicode:\\u0072,codepoint:U+0072},{char:l,unicode:\\u006C,codepoint:U+006C},{char:d,unicode:\\u0064,codepoint:U+0064}] |
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 | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
action | string | The action performed on the text (escape or unescape) | |
original | string | The original input text with escape sequences | |
escaped | string | The converted text with escape sequences applied or removed | |
character_count | number | Total number of characters in the result text | |
| [ ] Array items: | array[11] | Array of character data with Unicode escape sequences | |
â”” charPremium | string | Individual character from the converted text | |
â”” unicodePremium | string | Unicode escape sequence representation of the character | |
â”” codepointPremium | string | Unicode codepoint notation (e.g., U+0048) for the character |
Headers
Required and optional headers for Unicode Escape/Unescape API requests:
| Header Name | Required | Example Value | Description |
|---|---|---|---|
X-API-Key | required | your_api_key_here | Your APIVerve API key. Found in your dashboard under API Keys. |
Accept | optional | application/json | Specify response format: application/json (default), application/xml, or application/yaml |
User-Agent | optional | MyApp/1.0 | Identifies your application for analytics and debugging purposes |
X-Request-ID | optional | req_123456789 | Custom request identifier for tracking and debugging requests |
Cache-Control | optional | no-cache | Control caching behavior for the request and response |
GraphQL AccessALPHA
Access Unicode Escape/Unescape through GraphQL to combine it with other API calls in a single request. Query only the unicode escape/unescape data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
unicodeescape(
input: {
text: "Hello World"
action: "escape"
}
) {
action
original
escaped
character_count
unicode_points
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Unicode Escape/Unescape API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call Unicode Escape/Unescape directly from browser-based applications without proxy servers.
| CORS Header | Value | Description |
|---|---|---|
Access-Control-Allow-Origin | * | Accepts requests from any origin |
Access-Control-Allow-Methods | * | Accepts any HTTP method |
Access-Control-Allow-Headers | * | Accepts any request headers |
Browser Usage: You can call Unicode Escape/Unescape directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.
Rate Limiting
Unicode Escape/Unescape API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all Unicode Escape/Unescape users.
| Plan | Rate Limit | Description |
|---|---|---|
| Free | 5 requests/min | Hard rate limit enforced - exceeding will return 429 errors |
| Starter | No Limit | Production ready - standard traffic priority |
| Pro | No Limit | Production ready - preferred traffic priority |
| Mega | No Limit | Production ready - highest traffic priority |
Learn more about rate limiting →
Rate Limit Headers
When rate limits apply, each Unicode Escape/Unescape response includes headers to help you track your usage:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed per time window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the rate limit window resets |
Handling Rate Limits
Free Plan: When you exceed your rate limit, Unicode Escape/Unescape returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.
Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.
Best Practices for Unicode Escape/Unescape:
- Monitor the rate limit headers to track your Unicode Escape/Unescape usage (Free plan only)
- Cache unicode escape/unescape responses where appropriate to reduce API calls
- Upgrade to Pro or Mega for guaranteed no-throttle Unicode Escape/Unescape performance
Note: Unicode Escape/Unescape rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using Unicode Escape/Unescape on Free tier.
Error Codes
The Unicode Escape/Unescape API uses standard HTTP status codes to indicate success or failure:
| Code | Message | Description | Solution |
|---|---|---|---|
200 | OK | Request successful, data returned | No action needed - request was successful |
400 | Bad Request | Invalid request parameters or malformed request | Check required parameters and ensure values match expected formats |
401 | Unauthorized | Missing or invalid API key | Include x-api-key header with valid API key from dashboard |
403 | Forbidden | API key lacks permission or insufficient credits | Check credit balance in dashboard or upgrade plan |
429 | Too Many Requests | Rate limit exceeded (Free: 5 req/min) | Implement request throttling or upgrade to paid plan |
500 | Internal Server Error | Server error occurred | Retry request after a few seconds, contact support if persists |
503 | Service Unavailable | API temporarily unavailable | Wait and retry, check status page for maintenance updates |
Learn more about error handling →
Need help? Contact support with your X-Request-ID for assistance.
Integrate Unicode Escape/Unescape with SDKs
Get started quickly with official Unicode Escape/Unescape SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.
Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.
Integrate Unicode Escape/Unescape with No-Code API Tools
Connect the Unicode Escape/Unescape API to your favorite automation platform without writing code. Build workflows that leverage unicode escape/unescape data across thousands of apps.





All platforms use your same API key to access Unicode Escape/Unescape. Visit our integrations hub for step-by-step setup guides.
Frequently Asked Questions
How do I get an API key for Unicode Escape/Unescape?
How many credits does Unicode Escape/Unescape cost?
Each successful Unicode Escape/Unescape 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 escape/unescape lookups.
Can I use Unicode Escape/Unescape in production?
The free plan is for testing and development only. For production use of Unicode Escape/Unescape, 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 Escape/Unescape from a browser?
What happens if I exceed my Unicode Escape/Unescape credit limit?
When you reach your monthly credit limit, Unicode Escape/Unescape 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.



