Convert written color descriptions directly into color codes.
Text to Color converts natural language color names into hexadecimal color codes. Send descriptive color phrases to receive matching hex values and channel counts, with paid plans adding RGB, HSL, and CMYK formats.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"color": "turquoise",
"hex": "#66c8b8",
"rgb": "102, 200, 184",
"hsl": "170, 47, 59",
"cmyk": "49, 0, 8, 22",
"ansi16": 96,
"channels": {
"rgbChannels": 3,
"cmykChannels": 4,
"ansiChannels": 1,
"hexChannels": 1,
"hslChannels": 3
}
}
}
About the Text to Color API
Text to Color works by analyzing the text provided and converting it to a color code. It uses advanced algorithms to convert the text to a color code and returns the color code.
What people use it for
- E-Commerce Product Tagging
- Online retailers map user-submitted garment color descriptions directly to standardized hex codes for accurate catalog search filters.
- Generative Prompt Styling
- When users specify scene themes using casual phrases like ocean blue, design tools resolve the exact hex codes for canvas backgrounds.
- Chatbot UI Customization
- Transform conversational customer preferences into hex values on the fly to preview customized dashboard themes in client settings.
- Form Input Normalization
- Validate freeform color inputs from creative survey responses by converting spoken or written hues into unambiguous hexadecimal codes.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Text to Color
Same data, same APIVerve account, same credit balance — one key works on all of them.
How many color conversions does the Free plan cover?
Do I get RGB, HSL, and CMYK values on the Free plan?
What formats are returned for each converted color?
What kind of text can I pass to the conversion parameter?
Will my response include RGB and CMYK values if I stay on the Free tier?
Request parameters — GET /v1/texttocolor
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
colorRequired | string | turquoise | The text to convert the color from |
curl "https://api.apiverve.com/v1/texttocolor?color=turquoise" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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.
Response — GET /v1/texttocolor
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"color": "turquoise",
"hex": "#66c8b8",
"rgb": "102, 200, 184",
"hsl": "170, 47, 59",
"cmyk": "49, 0, 8, 22",
"ansi16": 96,
"channels": {
"rgbChannels": 3,
"cmykChannels": 4,
"ansiChannels": 1,
"hexChannels": 1,
"hslChannels": 3
}
}
}
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 |
|---|---|---|---|
color | string | "turquoise" | The color name derived from the natural language input |
hex | string | "#66c8b8" | The hexadecimal color code representation |
rgbPremium | string | "102, 200, 184" | The RGB color code representation as comma separated values |
hslPremium | string | "170, 47, 59" | The HSL color code representation as comma separated values |
cmykPremium | string | "49, 0, 8, 22" | The CMYK color code representation as comma separated values |
ansi16Premium | number | 96 | The ANSI 16-color code representation of the color |
channels | object | {...} | The number of channels each returned color model uses |
rgbChannels | number | 3 | Number of channels in the RGB color model |
cmykChannels | number | 4 | Number of channels in the CMYK color model |
ansiChannels | number | 1 | Number of channels in the ANSI color model |
hexChannels | number | 1 | Number of channels in the hexadecimal color model |
hslChannels | number | 3 | Number of channels in the HSL color model |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Text to Color calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/texttocolor
No SDK to install — this is a plain HTTPS call to /v1/texttocolor with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/texttocolor" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/texttocolor
Install the Node.js SDK, then call the Text to Color API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/texttocolorconst res = await fetch("https://api.apiverve.com/v1/texttocolor", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/texttocolor
Install the Python SDK, then call the Text to Color API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-texttocolorimport requests
res = requests.get(
"https://api.apiverve.com/v1/texttocolor",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/texttocolor
Install the C# / .NET SDK, then call the Text to Color API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.TexttoColorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/texttocolor");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/texttocolor
No SDK to install — this is a plain HTTPS call to /v1/texttocolor with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/texttocolor", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/texttocolor
No SDK to install — this is a plain HTTPS call to /v1/texttocolor with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/texttocolor");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/texttocolor
No SDK to install — this is a plain HTTPS call to /v1/texttocolor with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/texttocolor")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Text to Color form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Text to Color API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Text to Color API.
Data Conversion
- ASCII85 Encoder
- Base64 Encoder/Decoder
- Color Converter
- CSV to JSON Converter
- File Size Formatter
- HTML Entities Encoder/Decoder
- HTML to Image
- JSON to CSV Converter
- JSON to JSONP
- JWT Decoder
- Markdown Table Generator
- Markdown to HTML
- Markdown to Image
- Markdown to PDF
- Math Calculator
- Meeting Time Converter
- Number Base Converter
- Number to Words
- Placeholder Text Generator
- Punycode Converter
- Query String Builder
- Relative Time Formatter
- Roman Numeral Converter
- Text to Color
- Unicode Escape/Unescape
- Unit Converter
- Unix Timestamp Converter
- URL Encoder/Decoder
- URL to Markdown
- Variable Name Converter
- Website to Text
- Words to Numbers
- XML to JSON