Leet Speak API
Overview
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/leetspeakExample
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)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))
}{
"status": "ok",
"error": null,
"data": {
"text": "7h!5 !5 4 5!mp13 p!3c3 0f 73x7",
"mode": "encode",
"changedCharacters": 17
}
}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. 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>
<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
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 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 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
Leet Speak 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 Leet Speak 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 Leet Speak
Official Leet Speak packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Leet Speak works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See 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.








