{
"error":"Invalid API key","code":401,
"response_code":401,"response_time_ms":12
}
Response Codes
Code
Description
200 Success
Request processed OK.
400 Bad Request
Input validation failed.
401 Unauthorized
Missing / wrong API key.
403 Forbidden
Key inactive or not allowed.
429 Rate Limit
Too many requests.
500 Server Error
Unexpected failure.
transliterate
transliterator0.0090 credits
Parameters
API Key
query · string
· required
Language
query · string
Text
query · string
· required
Output type
query · string
Delimiter
query · string
Code Samples
Response
Status:—
Headers
Body
Transliterator API — Practical Guide
A hands-on guide to Transliterator API: what it does, when to use each mode,
the parameters that actually matter, and how to read responses for SEO slugs, filenames, app identifiers, and more.
Last updated: 21 Nov 2025, 19:55API Version: v1Burst: 20 req/sLatency: 12.5 msCost: 0.009 credits/req
Send a text in any supported script (e.g., Cyrillic, Greek) and get a clean Latin version and/or a
specific formatting: slug, snake_case, camelCase, Capital Case, UPPER, or lower.
Perfect for SEO URLs, file/ID normalization, search indexing, and consistent UI labels.
Added capital output type and improved auto-detection for mixed scripts.
Normalized duplicate separators in slug/snake.
2025-10-12
Custom delimiter now supported for both slug and snake.
Minor Cyrillic → Latin mapping refinements (BG/RU).
2025-10-01
Public v1 release with plain, slug, snake, camel, upper, lower.
Max input length set to 255 chars.
Frequently Asked Questions
We support full transliteration for 25+ scripts including Arabic, Cyrillic, Greek, Hebrew and CJK. Need another language? Contact us.
We use ISO or de-facto web standards. Accuracy is typically 95 %+ for common vocabulary.
Yes. Every request, even those resulting in errors, consumes credits. This is because your credits are tied to the number of requests, regardless of success or failure. If the error is clearly due to a platform problem on our end, we will restore the affected credits (no cash refunds).
Contact us at [email protected]. We take feedback seriously—if your bug report or feature request is meaningful, we can fix or improve the API quickly and grant you 50 free credits as a thank you.
It depends on the API and sometimes even on the endpoint. Some endpoints use data from external sources, which may have stricter limits. We also enforce limits to prevent abuse and keep our platform stable. Check the docs for the specific rate limit for each endpoint.
We operate on a credit system. Credits are prepaid, non-refundable units you spend on API calls and tools. Credits are consumed FIFO (oldest first) and are valid for 12 months from the purchase date. The dashboard shows each purchase date and its expiry.
Yes. All purchased credits (including fractional balances) are valid for 12 months from purchase. Unused credits automatically expire and are permanently deleted at the end of the validity period. Expired credits cannot be restored or converted to cash or other value. Transitional rule: credits bought before 22 Sep 2025 are treated as purchased on 22 Sep 2025 and expire on 22 Sep 2026 (unless an earlier expiry was stated at purchase).
Yes—within their validity window. Unused credits remain available and roll over month-to-month until they expire 12 months after purchase.
Credits are non-refundable. Only buy what you need—you can always top up later. If a platform-side error causes a failed charge, we may restore the affected credits after investigation. No cash refunds.
Prices are set in credits, not dollars. Each endpoint lists its own cost—see the “Credits / request” badge above. You’ll always know exactly what you’re spending.