Unicode Escape/Unescape API

Overview

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/unicodeescape

Example

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)

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))
}

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

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_here

Learn more about authentication →

Interactive 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:

Response

The Unicode Escape/Unescape 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 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

Response Structure

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

Learn more about response formats →

Response Data Fields

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

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 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/graphql

query {
  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 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 Escape/Unescape 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 Escape/Unescape 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 Escape/Unescape

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

JitPack

No-Code Integrations

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

Zapier

Make

Pipedream

n8n

Power Automate

Frequently Asked Questions

People who used this also used...

Based on your interest in Unicode Escape/Unescape, you might also like these APIs:

XML to JSON

XML to JSON is a simple tool for converting XML to JSON. It returns the JSON representation of the XML provided.

1 credit per call

Words to Numbers

Words to Numbers is a simple tool for converting words to numbers. It returns the words in numbers.

1 credit per call

Website to Text

Website to Text is a simple tool for converting a website to text. It returns the text extracted from the website.

10 credits per call