Sitemap Generator API

POST

Build search-engine-ready XML sitemaps from your URL lists.

Sitemap Generator creates valid XML sitemaps from URL lists following the sitemaps.org protocol for search engine optimization.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/sitemapgenerator

Body

urlsstring

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "sitemap": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<urlset xmlns=\"http://www.sitemaps.org/schemas/sitemap/0.9\">\n  <url>\n    <loc>https://example.com/</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.5</priority>\n  </url>\n  <url>\n    <loc>https://example.com/about</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.5</priority>\n  </url>\n  <url>\n    <loc>https://example.com/contact</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.5</priority>\n  </url>\n  <url>\n    <loc>https://example.com/blog</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>daily</changefreq>\n    <priority>0.8</priority>\n  </url>\n  <url>\n    <loc>https://example.com/products</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.9</priority>\n  </url>\n</urlset>",
    "urlCount": 5,
    "sizeBytes": 892,
    "sizeKb": 0.87,
    "format": "XML",
    "protocol": "sitemaps.org/0.9",
    "settings": {
      "defaultChangeFreq": "weekly",
      "defaultPriority": 0.5,
      "includeLastMod": true,
      "baseUrl": "https://example.com"
    }
  }
}

About the Sitemap Generator API

Generates properly formatted XML compliant with search engine requirements, supporting up to 50,000 URLs per sitemap.

What people use it for

SEO Optimization: Generate sitemaps to help search engines index website content
Website Management: Create and maintain XML sitemaps for content management systems
Build Automation: Integrate sitemap generation into website deployment pipelines
Multi-site Management: Generate sitemaps for multiple websites with custom configurations

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

View all integrations →

Other ways to use Sitemap Generator

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit

Questions.

Common questions about the Sitemap Generator API.

Read the docs →

How many sitemaps does the Free plan cover?

The Free plan gives you 200 credits each month, which generates 100 sitemaps. On the Starter plan, 100,000 sitemaps consume your monthly 200,000 credits, which works out to about $0.30 per 1,000 sitemaps.

Do I get sitemap file sizes on the Free plan?

No. Sitemap file size in bytes and kilobytes is reserved for paid plans starting with Starter. The Free plan returns the generated XML sitemap, URL count, protocol information, and applied configuration settings.

How many URLs can I include in a single sitemap?

You can supply up to 50,000 URLs in a single request. This aligns with the sitemaps.org specification limit for individual sitemap files.

Can I supply relative paths instead of full URLs?

Yes. You can provide relative paths along with a base URL parameter, and the generator automatically combines them into full absolute paths. You can pass URLs as plain strings or as objects containing individual priority, change frequency, and last modified values.

Does the generated XML follow the official sitemaps.org standard?

Yes. Sitemap Generator formats the XML to adhere strictly to the sitemaps.org protocol recognized by major search engines. It maps priority values, change frequencies, and last modified dates to standard schema tags.

Request parameters — POST /v1/sitemapgenerator

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
`urls`Required	array	`["/about", "/contact", {"url": "/blog", "priority": 0.8}]`	Array of URLs (strings or objects with url, priority, changeFreq, lastMod) url

Optional

Parameter	Type	Example	Description
`baseUrl`Optional	string	`https://example.com`	Base URL to prepend to relative paths url
`changeFreq`Optional	string	`weekly`	Default change frequency `alwayshourlydailyweeklymonthlyyearlynever` default weekly
`priority`Optional	number	`0.5`	Default priority default 0.5 · range 0-1
`includeLastMod`Optional	boolean	`true`	Include lastmod dates in sitemap default true

Example request

curl -X POST "https://api.apiverve.com/v1/sitemapgenerator" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["/","/about","/contact",{"url":"/blog","priority":0.8,"changeFreq":"daily"},{"url":"/products","priority":0.9}],"baseUrl":"https://example.com","changeFreq":"weekly","priority":0.5,"includeLastMod":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-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.
`content-type`Required	POST body	`application/json`

401 is the only auth verdict

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/sitemapgenerator

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.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "sitemap": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<urlset xmlns=\"http://www.sitemaps.org/schemas/sitemap/0.9\">\n  <url>\n    <loc>https://example.com/</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.5</priority>\n  </url>\n  <url>\n    <loc>https://example.com/about</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.5</priority>\n  </url>\n  <url>\n    <loc>https://example.com/contact</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.5</priority>\n  </url>\n  <url>\n    <loc>https://example.com/blog</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>daily</changefreq>\n    <priority>0.8</priority>\n  </url>\n  <url>\n    <loc>https://example.com/products</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.9</priority>\n  </url>\n</urlset>",
    "urlCount": 5,
    "sizeBytes": 892,
    "sizeKb": 0.87,
    "format": "XML",
    "protocol": "sitemaps.org/0.9",
    "settings": {
      "defaultChangeFreq": "weekly",
      "defaultPriority": 0.5,
      "includeLastMod": true,
      "baseUrl": "https://example.com"
    }
  }
}

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
`sitemap`	string	`"<?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <url> <loc>https://example.com/</…`	Generated XML sitemap content following sitemaps.org protocol
`urlCount`	number	`5`	Total number of URLs included in the generated sitemap
`sizeBytes`Premium	number	`892`	Total size of generated sitemap in bytes
`sizeKb`Premium	number	`0.87`	Total size of generated sitemap in kilobytes
`format`	string	`"XML"`	Output format type of generated sitemap content
`protocol`	string	`"sitemaps.org/0.9"`	Sitemap protocol version used for XML generation
`settings`	object	`{...}`
`defaultChangeFreq`	string	`"weekly"`	Default change frequency setting applied to all URLs
`defaultPriority`	number	`0.5`	Default priority value assigned to all URLs
`includeLastMod`	boolean	`true`	Flag indicating if last modified dates are included
`baseUrl`	string	`"https://example.com"`	Base URL used to create absolute paths for relative URLs

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	Sitemap Generator 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.

Compare all pricing tiers →

Call it from cURL — POST /v1/sitemapgenerator

No SDK to install — this is a plain HTTPS call to /v1/sitemapgenerator with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/sitemapgenerator" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/sitemapgenerator-apiSource, issues and the examples this page is built from.ReferenceSitemap Generator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/sitemapgeneratornpm apiverve-sitemapgeneratorPyPI APIVerve.API.SitemapGeneratorNuGet

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/sitemapgenerator

Install the Node.js SDK, then call the Sitemap Generator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/sitemapgenerator

Node.js

const res = await fetch("https://api.apiverve.com/v1/sitemapgenerator", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/sitemapgeneratorThe published Node.js client, versioned and signed.GitHubapiverve/sitemapgenerator-apiSource, issues and the examples this page is built from.ReferenceSitemap Generator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

apiverve-sitemapgeneratorPyPI APIVerve.API.SitemapGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — POST /v1/sitemapgenerator

Install the Python SDK, then call the Sitemap Generator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — PyPI

pip install apiverve-sitemapgenerator

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/sitemapgenerator",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

PyPIapiverve-sitemapgeneratorThe published Python client, versioned and signed.GitHubapiverve/sitemapgenerator-apiSource, issues and the examples this page is built from.ReferenceSitemap Generator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/sitemapgeneratornpm APIVerve.API.SitemapGeneratorNuGet

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/sitemapgenerator

Install the C# / .NET SDK, then call the Sitemap Generator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.SitemapGenerator

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/sitemapgenerator");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.SitemapGeneratorThe published C# / .NET client, versioned and signed.GitHubapiverve/sitemapgenerator-apiSource, issues and the examples this page is built from.ReferenceSitemap Generator API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/sitemapgeneratornpm apiverve-sitemapgeneratorPyPI

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — POST /v1/sitemapgenerator

No SDK to install — this is a plain HTTPS call to /v1/sitemapgenerator 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/sitemapgenerator", 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

@apiverve/sitemapgeneratornpm apiverve-sitemapgeneratorPyPI APIVerve.API.SitemapGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — POST /v1/sitemapgenerator

No SDK to install — this is a plain HTTPS call to /v1/sitemapgenerator with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/sitemapgenerator");
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

@apiverve/sitemapgeneratornpm apiverve-sitemapgeneratorPyPI APIVerve.API.SitemapGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — POST /v1/sitemapgenerator

No SDK to install — this is a plain HTTPS call to /v1/sitemapgenerator with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/sitemapgenerator")
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.body

Resources

Also published for

@apiverve/sitemapgeneratornpm apiverve-sitemapgeneratorPyPI APIVerve.API.SitemapGeneratorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Data Generation

View all 32 →

All articles →

Generate Barcodes for Inventory and ShippingCreate Code 128 and Code 39 barcodes programmatically. Tutorial for inventory systems, shipping labels, and asset tracking.Read

Add Secure Password Generation to Your AppGenerate cryptographically secure passwords via API. Tutorial with code examples for signup flows, admin panels, and password managers.Read

QR Codes Are Back (And This Time It's Different)Remember when QR codes were a punchline? Now they're everywhere. Here's why this time it stuck.Read

Sitemap Generator API

Try it — live request, no key required

About the Sitemap Generator API

What people use it for

Ways to call it

Other ways to use Sitemap Generator

Questions.

Request parameters — POST /v1/sitemapgenerator

Required

Optional

Authentication

Response — POST /v1/sitemapgenerator

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — POST /v1/sitemapgenerator

Resources

Also published for

Call it from Node.js — POST /v1/sitemapgenerator

Resources

Also published for

Call it from Python — POST /v1/sitemapgenerator

Resources

Also published for

Call it from C# / .NET — POST /v1/sitemapgenerator

Resources

Also published for

Call it from Go — POST /v1/sitemapgenerator

Resources

Also published for

Call it from PHP — POST /v1/sitemapgenerator

Resources

Also published for

Call it from Ruby — POST /v1/sitemapgenerator

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Sitemap Generator API

Data Generation

Related articles

Ready to build with Sitemap Generator? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog