Alphabetize any text list in ascending or descending order.
Line Sorter organizes text by sorting lines alphabetically in ascending or descending order with case-sensitive options.
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": {
"sorted": [
"An apple a day keeps the doctor away",
"banana",
"Cherry blossoms bloom in spring",
"date",
"The quick brown fox jumps over the lazy dog"
],
"lineCount": 5,
"order": "asc",
"caseSensitive": false
}
}
About the Line Sorter API
A line sorter API for putting lists in order without writing sort code. Send an array of text lines and get them back sorted, with control over direction and whether capital letters are treated differently from lowercase. Use it as a text sorter to sort any list alphabetically, A to Z or Z to A.
It suits cleaning up exported lists, alphabetizing names, tags, product titles or glossary terms, normalizing config and data files before diffing them, and sorting user-pasted lists in no-code tools and spreadsheets that lack a reliable alphabetical sort. By default the sort ignores case, so "apple", "Banana" and "cherry" come back in the order a reader expects.
The response returns the sorted lines, how many lines were sorted, and the order and case setting that were applied, so a workflow can confirm what it got. Every field is available on every plan, including the Free plan.
How it works
Line Sorter sorts the strings in lines and returns them as sorted. Every entry must be a string; a number, boolean or object anywhere in the array returns a 400 error that names the index of the first bad entry. Lines are not trimmed or split, and duplicates stay in the output unless unique is true, so leading spaces affect where a line lands. Set natural to true for numeric-aware order (item1, item2, item10 instead of item1, item10, item2); it uses locale collation in both case modes.
order is asc (the default) or desc. With caseSensitive false (the default) both lines are lowercased and compared with locale-aware collation, which places accented letters next to their base letters and orders digits before letters, giving a natural dictionary order. Lines that differ only in case keep their relative order.
With caseSensitive true the comparison switches to raw UTF-16 code-unit order. In that mode every uppercase ASCII letter sorts before every lowercase one, so ["b", "a", "C"] becomes ["C", "a", "b"], and accented letters sort after "z". Use it when you need a byte-style order that matches other tools, and the default when people will read the result.
lineCount is the number of lines returned (the number received unless unique dropped duplicates), order echoes the direction applied and caseSensitive is the boolean that was actually used; it accepts true, false or the strings "true" and "false". desc is the exact reverse comparison of asc in both modes. The response is identical on every plan.
What people use it for
- List Organization
- Sort and organize lists alphabetically for better readability and data management
- Data Cleanup
- Clean up and alphabetize data files with customizable sorting options
- Content Sorting
- Sort text content with case-sensitive or case-insensitive options
- File Processing
- Process and organize large text files with up to 10,000 lines
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 Line Sorter
Same data, same APIVerve account, same credit balance — one key works on all of them.
Why does item10 sort before item2, and how do I fix it?
What is the maximum number of lines I can sort in a single request?
Can I sort lines in reverse alphabetical order?
Can I ignore capitalization when alphabetizing text?
Does the response confirm how many lines were processed?
Which plan fits sorting 50,000 lists a month?
Request parameters — POST /v1/linesorter
Sent as JSON in the request body. 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 |
|---|---|---|---|
linesRequired | array | ["banana","apple","cherry"] | Array of text lines to sort (max 10,000) |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
orderOptional | string | asc | Sort orderascdescdefault asc |
caseSensitiveOptional | boolean | false | Enable case-sensitive sorting default false |
naturalOptional | boolean | false | Natural (numeric-aware) order: runs of digits compare as numbers, so item2 sorts before item10 default false |
uniqueOptional | boolean | false | Remove duplicate lines before sorting (case-insensitive unless caseSensitive is true); the first spelling is kept default false |
curl -X POST "https://api.apiverve.com/v1/linesorter" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"lines":["The quick brown fox jumps over the lazy dog","An apple a day keeps the doctor away","banana","Cherry blossoms bloom in spring","date"],"order":"asc","caseSensitive":false,"natural":true,"unique":true}'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. |
content-typeRequired | POST body | application/json |
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 — POST /v1/linesorter
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": {
"sorted": [
"An apple a day keeps the doctor away",
"banana",
"Cherry blossoms bloom in spring",
"date",
"The quick brown fox jumps over the lazy dog"
],
"lineCount": 5,
"order": "asc",
"caseSensitive": false
}
}
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 |
|---|---|---|---|
sorted | array | [An apple a day keeps the doctor away, ...] | Array of sorted text lines |
lineCount | number | 5 | Total number of lines sorted (after duplicates are removed when unique is true) |
order | string | "asc" | Sort order that was applied |
caseSensitive | boolean | false | Whether the sort compared case exactly; when false, lines are compared case-insensitively |
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 — 1 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 | Line Sorter calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 200 | Free |
| Starter | $29.99 | 200,000 | 200,000 | $0.15 |
| Pro | $99.99 | 1,000,000 | 1,000,000 | $0.10 |
| Mega | $299.99 | 4,000,000 | 4,000,000 | $0.07 |
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 — POST /v1/linesorter
No SDK to install — this is a plain HTTPS call to /v1/linesorter 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/linesorter" \
-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 — POST /v1/linesorter
Install the Node.js SDK, then call the Line Sorter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/linesorterconst res = await fetch("https://api.apiverve.com/v1/linesorter", {
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 — POST /v1/linesorter
No SDK to install — this is a plain HTTPS call to /v1/linesorter with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/linesorter",
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 — POST /v1/linesorter
Install the C# / .NET SDK, then call the Line Sorter 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.LineSorterusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/linesorter");
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 — POST /v1/linesorter
No SDK to install — this is a plain HTTPS call to /v1/linesorter 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/linesorter", 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 — POST /v1/linesorter
No SDK to install — this is a plain HTTPS call to /v1/linesorter 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/linesorter");
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 — POST /v1/linesorter
No SDK to install — this is a plain HTTPS call to /v1/linesorter 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/linesorter")
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 Line Sorter 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 — Line Sorter 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 Line Sorter API.
Text Processing
- Acronym Expander
- Anagram Detector
- Antonym Finder
- Cron Expression Parser
- Data Masking
- Did You Mean
- Emoji Decorator
- Gibberish Detector
- Grammar Check
- ISBN Validator
- JSON Schema Validator
- Keyword Extractor
- Leet Speak
- Levenshtein Distance
- Line Sorter
- Markdown Link Extractor
- Palindrome Checker
- Parts Of Speech
- Phonetic Encoder
- Pig Latin
- Profanity Filter
- Reading Time Calculator
- Regex Tester
- Remove Punctuation
- Reverse Text
- Rhyming Words
- Slugify
- Spell Checker
- Syllable Counter
- Tax ID Validator
- Tense Converter
- Text Language
- Text Lemmatizer
- Text Readability Score
- Text Similarity
- Text Styler
- Text Summarizer
- Text to Emoji
- Title Case Converter
- Translator
- Vowel Counter
- Website Readability
- Word Lexicon Analyzer
- Word Opposites
- Word Pronunciation
Related articles
All articles →
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read
Summarize Text with AI: A Practical GuideUse AI to summarize articles, documents, and user content. Tutorial with code for content platforms, research tools, and dashboards.Read
7 Content Moderation Mistakes That Sink AppsYour app allows user content. Here are the moderation mistakes that get apps pulled from stores.Read