Overview
Reverse Text applies one of three transformations to `text`, chosen with `mode`. The value must be `characters` (the default), `words` or `lines`.
In `characters` mode the string is split into user-perceived characters (grapheme clusters), reversed and joined, so "Hello World" becomes "dlroW olleH". Emoji, emoji sequences and letters with combining accents stay intact.
In `words` mode the words (runs of non-whitespace) are reversed into the original word positions, so every separator (spaces, runs of spaces, tabs, line breaks) stays exactly where it was. Punctuation stays attached to its word, so "Hello, world!" becomes "world! Hello,".
In `lines` mode the text is split on line feeds or Windows CRLF line endings, the lines are reversed and rejoined with the text's own line ending (CRLF if the text contains one, otherwise LF); the content of each line is unchanged.
`reversed` holds the result, `original` echoes the input and `mode` echoes the mode applied. `length` is the length of the original text in JavaScript string units, which equals the character count for plain text but counts each emoji as two. No trimming or normalization is applied in any mode. The response is the same on every plan.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl -X POST https://api.apiverve.com/v1/reversetext \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"text": "Hello World",
"mode": "characters"
}'const res = await fetch('https://api.apiverve.com/v1/reversetext', {
method: 'POST',
headers: {
'x-api-key': 'your_api_key_here',
'Content-Type': 'application/json',
},
body: JSON.stringify({
"text": "Hello World",
"mode": "characters"
}),
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.post(
"https://api.apiverve.com/v1/reversetext",
headers={"x-api-key": "your_api_key_here"},
json={
"text": "Hello World",
"mode": "characters"
},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
"strings"
)
func main() {
body := strings.NewReader(`{
"text": "Hello World",
"mode": "characters"
}`)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/reversetext", body)
req.Header.Set("Content-Type", "application/json")
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
textRequired | string | Text to reverse |
modeOptional | string | Reversal modecharacterswordslinesdefault characters |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"reversed": "dlroW olleH",
"original": "Hello World",
"mode": "characters",
"length": 11
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
reversed | string | "dlroW olleH" | Reversed text result |
original | string | "Hello World" | Original input text |
mode | string | "characters" | Reversal mode that was applied |
length | number | 11 | Character length of the original text |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Text Effects
- Create reversed text effects for creative content and visual designs
- String Manipulation
- Reverse strings for data processing and algorithm testing
- Content Transformation
- Transform text content with different reversal modes for specific formatting needs
- Data Processing
- Process and reverse text data for analysis and transformation tasks
Other ways to use Reverse Text
Set up Reverse Text on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Text Processing: