Developer API
There isn't one. This page says so plainly rather than documenting something that does not answer.
What used to be on this page
Until 2026-08-11 this page described a REST API at https://api.texttoolz.com/v1/
with Bearer-token authentication, per-plan rate limits and four endpoints. That subdomain
has no DNS record, no key was ever issued, and the plans the keys were supposedly attached
to did not exist either. All of it has been removed.
Why there is no API
Every tool here runs in your browser. Paste text into a tool page and the conversion happens in JavaScript on your own machine: nothing is uploaded, stored or logged. That is a deliberate privacy property, and it also means there is no server-side function sitting behind these tools that could be exposed as an endpoint.
Automating these conversions yourself
Nearly everything on this site is a short piece of code in any language:
- Base64 and URL encoding: standard library in every language.
- Case conversion, trimming, line handling: built-in string methods.
- Unicode text styles (bold, script, bubble, small caps): a character map from ASCII to the matching Unicode block, applied per character.
- Encoding inspection: codepoint iteration; the invisible character detector shows the codepoints it looks for.
The tool pages are useful as a reference implementation: run your output and theirs on the same input and compare.
If you need one
Tell us what you would call and why: contact form. A real endpoint would be announced here, with a working request you can paste into a terminal.
Frequently Asked Questions
Is there a TextToolz API?
No. There is no public API, no API key and no api.texttoolz.com endpoint. This page used to document one; none of it was ever running.
Why is there no API?
Every tool on the site runs in the visitor's browser in JavaScript. Nothing is processed server-side, so there is no server function to expose as an endpoint.
How can I automate a conversion then?
Most of these transformations are a few lines in your own language of choice: Unicode styling is a character map, Base64 and URL encoding are standard library calls, and case conversion is built in. Use the tool pages to check your output against a reference implementation.
Other Tools You Might Like
The tools below come from the same category as the one you are using, so they work on the same kind of text.
Generate random addresses for testing
Repeat any word, line or paragraph with the separator you choose.
Count how often each word appears, ranked with its share of the text.
Combine multiple text strings into one
Browse Categories
Every tool on the site belongs to one of the categories below, grouped by the job it does rather than by the format it reads.