Overview
Slugify works by normalizing text, removing accents, stripping special characters, and replacing spaces with separators. Supports both hyphen and underscore separators with optional lowercase conversion.
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/slugify \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"text": "Hello World! This is a Test & Example",
"separator": "-",
"lowercase": true
}'const res = await fetch('https://api.apiverve.com/v1/slugify', {
method: 'POST',
headers: {
'x-api-key': 'your_api_key_here',
'Content-Type': 'application/json',
},
body: JSON.stringify({
"text": "Hello World! This is a Test & Example",
"separator": "-",
"lowercase": true
}),
});
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/slugify",
headers={"x-api-key": "your_api_key_here"},
json={
"text": "Hello World! This is a Test & Example",
"separator": "-",
"lowercase": True
},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
"strings"
)
func main() {
body := strings.NewReader(`{
"text": "Hello World! This is a Test & Example",
"separator": "-",
"lowercase": true
}`)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/slugify", 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 a slug |
separatorOptional | string | The separator character-_default - |
lowercaseOptional | boolean | Convert to lowercase (default: true) default true |
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": {
"original": "Hello World! This is a Test & Example",
"slug": "hello-world-this-is-a-test-example",
"separator": "-",
"lowercase": true,
"length": 34
}
}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 |
|---|---|---|---|
original | string | "Hello World! This is a Test & Example" | Original input text before slugification |
slug | string | "hello-world-this-is-a-test-example" | URL-friendly slug generated from the input text |
separator | string | "-" | |
lowercase | boolean | true | |
length | number | 34 |
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
- URL Generation
- Create SEO-friendly URLs for blog posts, articles, and product pages from titles
- File Naming
- Generate safe filenames from user input or document titles for file storage systems
- Database Keys
- Create readable, URL-safe identifiers for database records and API resources
- Link Management
- Generate clean, shareable links for content that are both readable and SEO-optimized
Other ways to use Slugify
Set up Slugify 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: