Overview
Title Capitalization works by analyzing the title text provided and converting it to various cases. It uses advanced algorithms to convert the text to title cases based on your requirements.
Live Test Title Case Converter 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.
curl -X POST https://api.apiverve.com/v1/titlecapitalization \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"text": "comprehensive analysis of quarterly financial performance and strategic initiatives for sustainable growth",
"style": "title-case"
}'const res = await fetch('https://api.apiverve.com/v1/titlecapitalization', {
method: 'POST',
headers: {
'x-api-key': 'your_api_key_here',
'Content-Type': 'application/json',
},
body: JSON.stringify({
"text": "comprehensive analysis of quarterly financial performance and strategic initiatives for sustainable growth",
"style": "title-case"
}),
});
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/titlecapitalization",
headers={"x-api-key": "your_api_key_here"},
json={
"text": "comprehensive analysis of quarterly financial performance and strategic initiatives for sustainable growth",
"style": "title-case"
},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
"strings"
)
func main() {
body := strings.NewReader(`{
"text": "comprehensive analysis of quarterly financial performance and strategic initiatives for sustainable growth",
"style": "title-case"
}`)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/titlecapitalization", 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 | The text to convert to title case |
styleRequired | string | The case to convert the text toapachicagoapmlanytamabbwikipedia+8 |
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": {
"style": "title-case",
"text": "Comprehensive Analysis of Quarterly Financial Performance and Strategic Initiatives for Sustainable Growth"
}
}
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 |
|---|---|---|---|
style | string | "title-case" | The selected case style applied to the text |
text | string | "Comprehensive Analysis of Quarterly Financial Performance and Strategic Initiatives for Sustainable Growth" | The converted text in the requested case style |
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
- Editorial Style Enforcement
- Editorial desks format draft article headlines to Chicago or AP rules automatically before publishing to the live site.
- Citation Bibliography Formatting
- Reference management software converts uploaded paper titles to APA or MLA casing before building bibliography export files.
- Campaign Subject Normalization
- When scheduling outbound broadcasts, email tools pass draft subject lines through the API to enforce uniform sentence-case styling.
- Technical Documentation Linting
- To maintain uniform guides, build pipelines convert markdown section headings into matching APA or sentence case styles during deployment.
Other ways to use Title Case Converter
Set up Title Case Converter 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: