Text Styler

Overview

Text Styler maps `text` through one of the transformation functions in the @viper-x/fancytext library, selected by `style`. The style name is matched case-insensitively, and values outside the documented list are rejected with a 400 error before any styling runs. The twenty accepted values are strikeThrough, tildeStrikeThrough, slashThrough, underline, doubleUnderline, crossAboveBelow, arrowBelow, heartsBetween, creepify, wingdings, vaporwave, typewriter, analucia, sparrow, bubbles, squares, roundsquares, mirror, flip and tiny.

The styles fall into two groups. Substitution styles such as bubbles, squares, roundsquares, tiny, vaporwave, typewriter, sparrow, analucia and wingdings replace each supported character with a look-alike from another Unicode block, so characters without a mapping, usually digits or punctuation in some styles, pass through unchanged. Combining styles such as strikeThrough, underline, doubleUnderline, slashThrough, arrowBelow and crossAboveBelow keep the original characters and add a combining mark after every one of them, spaces included, while creepify stacks random combining marks above and below letters, and heartsBetween inserts a ♥ between every pair of characters.

The output in `text` is plain Unicode. Its length in characters is usually longer than the input, especially for combining styles, so check any character limits on the platform you post to. Screen readers may read substituted characters by their Unicode names, which matters for accessibility. Rendering depends on the reader's fonts: combining marks can stack differently across platforms.

`style` echoes the style value you sent and is null on the Free plan; `text` is returned on every plan.

Live Test Text Styler API →

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.

1
2
3
4
5
6
7

curl -X POST https://api.apiverve.com/v1/textstyler \
  -H "x-api-key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "text": "This is a very stylish piece of text",
  "style": "bubbles"
}'

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

const res = await fetch('https://api.apiverve.com/v1/textstyler', {
  method: 'POST',
  headers: {
    'x-api-key': 'your_api_key_here',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "text": "This is a very stylish piece of text",
  "style": "bubbles"
}),
});

if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);

const { data } = await res.json();
console.log(data);

1
2
3
4
5
6
7
8
9
10
11
12
13
14

import requests

res = requests.post(
    "https://api.apiverve.com/v1/textstyler",
    headers={"x-api-key": "your_api_key_here"},
    json={
    "text": "This is a very stylish piece of text",
    "style": "bubbles"
},
    timeout=15,
)
res.raise_for_status()

print(res.json()["data"])

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

package main

import (
	"fmt"
	"io"
	"net/http"
	"strings"
)

func main() {
	body := strings.NewReader(`{
  "text": "This is a very stylish piece of text",
  "style": "bubbles"
}`)
	req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/textstyler", 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.

Parameters

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.

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.

1
2
3
4
5
6
7
8

{
  "status": "ok",
  "error": null,
  "data": {
    "style": "bubbles",
    "text": "Ⓣⓗⓘⓢ ⓘⓢ ⓐ ⓥⓔⓡⓨ ⓢⓣⓨⓛⓘⓢⓗ ⓟⓘⓔⓒⓔ ⓞⓕ ⓣⓔⓧⓣ"
  }
}

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.

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.

Use cases

Social Media Formatting

Social media schedulers convert regular draft copy into bubble or underlined text to make promotional headlines stand out in feeds.

Chatbot Message Accents

When generating conversational replies, messaging bots apply slash-through or vaporwave formatting to highlight jokes, discounts, or canceled items.

Gaming Profile Names

Gaming communities transform member handles into decorative text using styles like creepify or cross accents during clan registration.

Email Newsletter Emphases

Generate eye-catching email subject lines by transforming key announcement phrases into typewriter or double-underlined character sets before sending.

Other ways to use Text Styler

Set up Text Styler 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: