Reverse paragraph order
Reverse Paragraph Order rearranges a piece of plain text from its final paragraph back to its first without reversing words, sentences, or characters inside any paragraph.
Run — free
Paste text whose paragraphs are separated by blank lines, and the tool returns the same blocks in the opposite sequence with a consistent blank line between them. Internal line breaks remain attached to their paragraph, so wrapped quotations, addresses, lists, and other multiline blocks stay together. The operation is deterministic, local, and useful when an outline, draft, transcript, or exported set of notes arrived in exactly the wrong section order.
How to use it
Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.
Check your inputs
Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.
Use it again or automate it
Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.
What you can do with it
Get an answer now
Enter one set of values and see the result without building a spreadsheet or script.
Compare scenarios
Change one value at a time and rerun the calculation to understand what affects the result.
Automate repeated work
Use the API when the same calculation needs to run inside your product or workflow.
FAQ
How do I use this capability?
Complete the fields above and run it on this page. The form highlights anything that needs attention.
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/str/reverse-paragraphs \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"Introduction comes first.\n\nSupporting details come second.\n\nConclusion comes last."}'const res = await fetch("https://api.kit.forhosting.com/str/reverse-paragraphs", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "Introduction comes first.\n\nSupporting details come second.\n\nConclusion comes last."
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/str/reverse-paragraphs",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "Introduction comes first.\n\nSupporting details come second.\n\nConclusion comes last."
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/str/reverse-paragraphs", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"Introduction comes first.\\n\\nSupporting details come second.\\n\\nConclusion comes last."}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"Introduction comes first.\n\nSupporting details come second.\n\nConclusion comes last."}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/str/reverse-paragraphs", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"text": "Introduction comes first.\n\nSupporting details come second.\n\nConclusion comes last."
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "str.reverse_paragraphs",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_chars | 100000 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |