Sitemap Generator API
Sitemap Generator creates valid XML sitemaps from URL lists following the sitemaps.org protocol for search engine optimization.
The Sitemap Generator API provides reliable and fast access to sitemap generator data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.
To use Sitemap Generator, you need an API key. You can get one by creating a free account and visiting your dashboard.
POST Endpoint
https://api.apiverve.com/v1/sitemapgeneratorCode Examples
Here are examples of how to call the Sitemap Generator API in different programming languages:
curl -X POST \
"https://api.apiverve.com/v1/sitemapgenerator" \
-H "X-API-Key: your_api_key_here" \
-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
}'const response = await fetch('https://api.apiverve.com/v1/sitemapgenerator', {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
},
body: JSON.stringify({
"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
})
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
payload = {
"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
}
response = requests.post('https://api.apiverve.com/v1/sitemapgenerator', headers=headers, json=payload)
data = response.json()
print(data)const https = require('https');
const url = require('url');
const options = {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
};
const postData = JSON.stringify({
"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
});
const req = https.request('https://api.apiverve.com/v1/sitemapgenerator', options, (res) => {
let data = '';
res.on('data', (chunk) => data += chunk);
res.on('end', () => console.log(JSON.parse(data)));
});
req.write(postData);
req.end();<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/sitemapgenerator');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'POST');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
'X-API-Key: your_api_key_here',
'Content-Type: application/json'
]);
curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode({
'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
}));
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);
?>package main
import (
"fmt"
"io"
"net/http"
"bytes"
"encoding/json"
)
func main() {
payload := map[string]interface{}{
"urls": "/,/about,/contact,[object Object],[object Object]",
"baseUrl": "https://example.com",
"changeFreq": "weekly",
"priority": "0.5",
"includeLastMod": "true"
}
jsonPayload, _ := json.Marshal(payload)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/sitemapgenerator", bytes.NewBuffer(jsonPayload))
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}require 'net/http'
require 'json'
uri = URI('https://api.apiverve.com/v1/sitemapgenerator')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
payload = {
"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
}
request = Net::HTTP::Post.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'
request.body = payload.to_json
response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;
class Program
{
static async Task Main(string[] args)
{
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");
var jsonContent = @"{
""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
}";
var content = new StringContent(jsonContent, Encoding.UTF8, "application/json");
var response = await client.PostAsync("https://api.apiverve.com/v1/sitemapgenerator", content);
response.EnsureSuccessStatusCode();
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);
}
}Authentication
The Sitemap Generator API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Sitemap Generator API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Sitemap Generator API:
Generate Sitemap
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
urls | array | required | Array of URLs (strings or objects with url, priority, changeFreq, lastMod) Format: url (e.g., ["/about", "/contact", {"url": "/blog", "priority": 0.8}]) | - | |
baseUrl | string | optional | Base URL to prepend to relative paths Format: url (e.g., https://example.com) | - | |
changeFreq | string | optional | Default change frequency Supported values: alwayshourlydailyweeklymonthly | ||
priority | number | optional | Default priority Range: 0 - 1 | ||
includeLastMod | boolean | optional | Include lastmod dates in sitemap |
Response
The Sitemap Generator API returns responses in JSON, XML, YAML, and CSV formats:
Example Responses
{
"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"
}
}
}<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<sitemap><?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2025-12-16</lastmod>
<changefreq>weekly</changefreq>
<priority>0.5</priority>
</url>
<url>
<loc>https://example.com/about</loc>
<lastmod>2025-12-16</lastmod>
<changefreq>weekly</changefreq>
<priority>0.5</priority>
</url>
<url>
<loc>https://example.com/contact</loc>
<lastmod>2025-12-16</lastmod>
<changefreq>weekly</changefreq>
<priority>0.5</priority>
</url>
<url>
<loc>https://example.com/blog</loc>
<lastmod>2025-12-16</lastmod>
<changefreq>daily</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/products</loc>
<lastmod>2025-12-16</lastmod>
<changefreq>weekly</changefreq>
<priority>0.9</priority>
</url>
</urlset></sitemap>
<urlCount>5</urlCount>
<sizeBytes>892</sizeBytes>
<sizeKb>0.87</sizeKb>
<format>XML</format>
<protocol>sitemaps.org/0.9</protocol>
<settings>
<defaultChangeFreq>weekly</defaultChangeFreq>
<defaultPriority>0.5</defaultPriority>
<includeLastMod>true</includeLastMod>
<baseUrl>https://example.com</baseUrl>
</settings>
</data>
</response>
status: ok
error: null
data:
sitemap: |-
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2025-12-16</lastmod>
<changefreq>weekly</changefreq>
<priority>0.5</priority>
</url>
<url>
<loc>https://example.com/about</loc>
<lastmod>2025-12-16</lastmod>
<changefreq>weekly</changefreq>
<priority>0.5</priority>
</url>
<url>
<loc>https://example.com/contact</loc>
<lastmod>2025-12-16</lastmod>
<changefreq>weekly</changefreq>
<priority>0.5</priority>
</url>
<url>
<loc>https://example.com/blog</loc>
<lastmod>2025-12-16</lastmod>
<changefreq>daily</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/products</loc>
<lastmod>2025-12-16</lastmod>
<changefreq>weekly</changefreq>
<priority>0.9</priority>
</url>
</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
| key | value |
|---|---|
| sitemap | <?xml version=1.0 encoding=UTF-8?> |
| <urlset xmlns=http://www.sitemaps.org/schemas/sitemap/0.9> | |
| <url> | |
| <loc>https://example.com/</loc> | |
| <lastmod>2025-12-16</lastmod> | |
| <changefreq>weekly</changefreq> | |
| <priority>0.5</priority> | |
| </url> | |
| <url> | |
| <loc>https://example.com/about</loc> | |
| <lastmod>2025-12-16</lastmod> | |
| <changefreq>weekly</changefreq> | |
| <priority>0.5</priority> | |
| </url> | |
| <url> | |
| <loc>https://example.com/contact</loc> | |
| <lastmod>2025-12-16</lastmod> | |
| <changefreq>weekly</changefreq> | |
| <priority>0.5</priority> | |
| </url> | |
| <url> | |
| <loc>https://example.com/blog</loc> | |
| <lastmod>2025-12-16</lastmod> | |
| <changefreq>daily</changefreq> | |
| <priority>0.8</priority> | |
| </url> | |
| <url> | |
| <loc>https://example.com/products</loc> | |
| <lastmod>2025-12-16</lastmod> | |
| <changefreq>weekly</changefreq> | |
| <priority>0.9</priority> | |
| </url> | |
| </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 Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
sitemap | string | - | |
urlCount | number | - | |
sizeBytes | number | - | |
sizeKb | number | - | |
format | string | - | |
protocol | string | - | |
settings | object | - | |
â”” defaultChangeFreq | string | - | |
â”” defaultPriority | number | - | |
â”” includeLastMod | boolean | - | |
â”” baseUrl | string | - |
Headers
Required and optional headers for Sitemap Generator API requests:
| Header Name | Required | Example Value | Description |
|---|---|---|---|
X-API-Key | required | your_api_key_here | Your APIVerve API key. Found in your dashboard under API Keys. |
Accept | optional | application/json | Specify response format: application/json (default), application/xml, or application/yaml |
User-Agent | optional | MyApp/1.0 | Identifies your application for analytics and debugging purposes |
X-Request-ID | optional | req_123456789 | Custom request identifier for tracking and debugging requests |
Cache-Control | optional | no-cache | Control caching behavior for the request and response |
GraphQL AccessALPHA
Access Sitemap Generator through GraphQL to combine it with other API calls in a single request. Query only the sitemap generator data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
sitemapgenerator(
input: {
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
}
) {
sitemap
urlCount
sizeBytes
sizeKb
format
protocol
settings {
defaultChangeFreq
defaultPriority
includeLastMod
baseUrl
}
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Sitemap Generator API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call Sitemap Generator directly from browser-based applications without proxy servers.
| CORS Header | Value | Description |
|---|---|---|
Access-Control-Allow-Origin | * | Accepts requests from any origin |
Access-Control-Allow-Methods | * | Accepts any HTTP method |
Access-Control-Allow-Headers | * | Accepts any request headers |
Browser Usage: You can call Sitemap Generator directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.
Rate Limiting
Sitemap Generator API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all Sitemap Generator users.
| Plan | Rate Limit | Description |
|---|---|---|
| Free | 5 requests/min | Hard rate limit enforced - exceeding will return 429 errors |
| Starter | No Limit | Production ready - standard traffic priority |
| Pro | No Limit | Production ready - preferred traffic priority |
| Mega | No Limit | Production ready - highest traffic priority |
Learn more about rate limiting →
Rate Limit Headers
When rate limits apply, each Sitemap Generator response includes headers to help you track your usage:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed per time window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the rate limit window resets |
Handling Rate Limits
Free Plan: When you exceed your rate limit, Sitemap Generator returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.
Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.
Best Practices for Sitemap Generator:
- Monitor the rate limit headers to track your Sitemap Generator usage (Free plan only)
- Cache sitemap generator responses where appropriate to reduce API calls
- Upgrade to Pro or Mega for guaranteed no-throttle Sitemap Generator performance
Note: Sitemap Generator rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using Sitemap Generator on Free tier.
Error Codes
The Sitemap Generator API uses standard HTTP status codes to indicate success or failure:
| Code | Message | Description | Solution |
|---|---|---|---|
200 | OK | Request successful, data returned | No action needed - request was successful |
400 | Bad Request | Invalid request parameters or malformed request | Check required parameters and ensure values match expected formats |
401 | Unauthorized | Missing or invalid API key | Include x-api-key header with valid API key from dashboard |
403 | Forbidden | API key lacks permission or insufficient credits | Check credit balance in dashboard or upgrade plan |
429 | Too Many Requests | Rate limit exceeded (Free: 5 req/min) | Implement request throttling or upgrade to paid plan |
500 | Internal Server Error | Server error occurred | Retry request after a few seconds, contact support if persists |
503 | Service Unavailable | API temporarily unavailable | Wait and retry, check status page for maintenance updates |
Learn more about error handling →
Need help? Contact support with your X-Request-ID for assistance.
Integrate Sitemap Generator with SDKs
Get started quickly with official Sitemap Generator SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.
Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.
Integrate Sitemap Generator with No-Code API Tools
Connect the Sitemap Generator API to your favorite automation platform without writing code. Build workflows that leverage sitemap generator data across thousands of apps.





All platforms use your same API key to access Sitemap Generator. Visit our integrations hub for step-by-step setup guides.
Frequently Asked Questions
How do I get an API key for Sitemap Generator?
How many credits does Sitemap Generator cost?
Each successful Sitemap Generator API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful sitemap generator lookups.
Can I use Sitemap Generator in production?
The free plan is for testing and development only. For production use of Sitemap Generator, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Sitemap Generator from a browser?
What happens if I exceed my Sitemap Generator credit limit?
When you reach your monthly credit limit, Sitemap Generator API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.



