{"type":"urlset","url":"https://www.sitemaps.org/sitemap.xml","count":50,"truncated":true,"urls":[{"loc":"https://www.sitemaps.org/","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/protocol.html","lastmod":"2022-12-15"},{"loc":"https://www.sitemaps.org/faq.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/terms.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/da/","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/da/protocol.html","lastmod":"2022-12-15"},{"loc":"https://www.sitemaps.org/da/faq.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/da/terms.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/de/","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/de/protocol.html","lastmod":"2022-12-15"},{"loc":"https://www.sitemaps.org/de/faq.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/de/terms.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/en_GB/","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/en_GB/protocol.html","lastmod":"2022-12-15"},{"loc":"https://www.sitemaps.org/en_GB/faq.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/en_GB/terms.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/es/","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/es/protocol.html","lastmod":"2022-12-15"},{"loc":"https://www.sitemaps.org/es/faq.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/es/terms.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/fi/","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/fi/protocol.html","lastmod":"2022-12-15"},{"loc":"https://www.sitemaps.org/fi/faq.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/fi/terms.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/fr/","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/fr/protocol.html","lastmod":"2022-12-15"},{"loc":"https://www.sitemaps.org/fr/faq.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/fr/terms.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/it/","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/it/protocol.html","lastmod":"2022-12-15"},{"loc":"https://www.sitemaps.org/it/faq.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/it/terms.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/ja/","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/ja/protocol.html","lastmod":"2022-12-15"},{"loc":"https://www.sitemaps.org/ja/faq.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/ja/terms.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/ko/","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/ko/protocol.html","lastmod":"2022-12-15"},{"loc":"https://www.sitemaps.org/ko/faq.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/ko/terms.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/nl/","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/nl/protocol.html","lastmod":"2022-12-15"},{"loc":"https://www.sitemaps.org/nl/faq.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/nl/terms.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/no/","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/no/protocol.html","lastmod":"2022-12-15"},{"loc":"https://www.sitemaps.org/no/faq.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/no/terms.html","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/pl/","lastmod":"2016-11-21"},{"loc":"https://www.sitemaps.org/pl/protocol.html","lastmod":"2022-12-15"}]}
curl --location --request GET 'https://zylalabs.com/api/13162/sitemap+parser+and+generator+api/26708/parse+a+sitemap' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Sitemap Parser and Generator API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
Read and write sitemaps without touching a parser library. One endpoint turns any sitemap or sitemap index into structured entries; the companion endpoint generates a valid sitemap file from a simple list of addresses.
Useful for crawlers and audits that start from a sitemap, site migrations comparing address sets, generating sitemaps for static sites, and checking content freshness across a large site.
The "Parse a Sitemap" endpoint returns structured data including the sitemap type, entry count, and detailed entries. Each entry contains the URL, last modification date, change frequency, and priority values.
Key fields in the response include "type" (sitemap type), "count" (number of entries), "truncated" (indicating if results are incomplete), and "urls" (an array of entries with their respective details).
The response data is organized in a JSON format. It includes a main object with metadata (type, count, truncated) and an array of URLs, each containing fields like "loc," "lastmod," "changefreq," and "priority."
The endpoint provides information about the sitemap's structure, including URLs, their last modification dates, change frequencies, and priority levels, allowing users to analyze and audit website content.
Users can customize their requests by specifying the URL of the sitemap they wish to parse. The API automatically handles compressed sitemaps and follows child sitemaps if they are part of an index.
Typical use cases include web crawlers analyzing site structure, audits for content freshness, generating sitemaps for static sites, and comparing address sets during site migrations.
Data accuracy is maintained by parsing sitemaps directly from their source, ensuring that the information reflects the most current state of the website as defined in the sitemap.
If results are truncated or empty, users should check the "truncated" field in the response. For incomplete data, consider revisiting the sitemap or checking for additional child sitemaps that may contain more entries.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund