Leet Speak API
Leet Speak is a simple tool for encoding and decoding Leet Speak. It returns the encoded or decoded Leet Speak.
The Leet Speak API provides reliable and fast access to leet speak data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.
To use Leet Speak, 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/leetspeakCode Examples
Here are examples of how to call the Leet Speak API in different programming languages:
curl -X POST \
"https://api.apiverve.com/v1/leetspeak" \
-H "X-API-Key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"text": "This is a simple piece of text",
"mode": "encode"
}'const response = await fetch('https://api.apiverve.com/v1/leetspeak', {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
},
body: JSON.stringify({
"text": "This is a simple piece of text",
"mode": "encode"
})
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
payload = {
"text": "This is a simple piece of text",
"mode": "encode"
}
response = requests.post('https://api.apiverve.com/v1/leetspeak', 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": "This is a simple piece of text",
"mode": "encode"
});
const req = https.request('https://api.apiverve.com/v1/leetspeak', 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/leetspeak');
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': 'This is a simple piece of text',
'mode': 'encode'
}));
$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": "This is a simple piece of text",
"mode": "encode"
}
jsonPayload, _ := json.Marshal(payload)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/leetspeak", 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/leetspeak')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
payload = {
"text": "This is a simple piece of text",
"mode": "encode"
}
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"": ""This is a simple piece of text"",
""mode"": ""encode""
}";
var content = new StringContent(jsonContent, Encoding.UTF8, "application/json");
var response = await client.PostAsync("https://api.apiverve.com/v1/leetspeak", content);
response.EnsureSuccessStatusCode();
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);
}
}Authentication
The Leet Speak 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 Leet Speak API directly in your browser with live requests and responses.
Parameters
The Leet Speak API supports multiple query options. Use one of the following:
Option 1: Encode Leet Speak
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
text | string | required | The text to encode or decode in Leet Speak | - | |
mode | string | required | The mode to use Supported values: encodedecode | - |
Option 2: Decode Leet Speak
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
text | string | required | The Leet Speak text to decode | - | |
mode | string | required | The mode to use Supported values: encodedecode |
Response
The Leet Speak API returns responses in JSON, XML, YAML, and CSV formats:
Example Responses
{
"status": "ok",
"error": null,
"data": {
"text": "7h!5 !5 4 5!mp13 p!3c3 0f 73x7",
"mode": "encode",
"changedCharacters": 17
}
}<?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>
<text>7h!5 !5 4 5!mp13 p!3c3 0f 73x7</text>
<mode>encode</mode>
<changedCharacters>17</changedCharacters>
</data>
</response>
status: ok
error: null
data:
text: 7h!5 !5 4 5!mp13 p!3c3 0f 73x7
mode: encode
changedCharacters: 17
| key | value |
|---|---|
| text | 7h!5 !5 4 5!mp13 p!3c3 0f 73x7 |
| mode | encode |
| changedCharacters | 17 |
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 |
|---|---|---|---|
text | string | - | |
mode | string | - | |
changedCharacters | number | - |
Headers
Required and optional headers for Leet Speak 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 Leet Speak through GraphQL to combine it with other API calls in a single request. Query only the leet speak 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 {
leetspeak(
input: {
text: "This is a simple piece of text"
mode: "encode"
}
) {
text
mode
changedCharacters
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Leet Speak API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call Leet Speak 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 Leet Speak directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.
Rate Limiting
Leet Speak API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all Leet Speak 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 Leet Speak 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, Leet Speak 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 Leet Speak:
- Monitor the rate limit headers to track your Leet Speak usage (Free plan only)
- Cache leet speak responses where appropriate to reduce API calls
- Upgrade to Pro or Mega for guaranteed no-throttle Leet Speak performance
Note: Leet Speak rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using Leet Speak on Free tier.
Error Codes
The Leet Speak 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 Leet Speak with SDKs
Get started quickly with official Leet Speak 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 Leet Speak with No-Code API Tools
Connect the Leet Speak API to your favorite automation platform without writing code. Build workflows that leverage leet speak data across thousands of apps.





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



