Sitemap Change Orchestrator
Pricing
Pay per usage
Sitemap Change Orchestrator
Monitor website sitemaps for new, updated, or removed URLs. Integration with the Website Content Crawler (WCC) allows feeding only relevant URLs. This ensures your web crawls are efficient, targeted, and resource-optimized, keeping your datasets fresh for any application.
0.0 (0)
Pricing
Pay per usage
1
Total users
2
Monthly users
2
Runs succeeded
88%
Last modified
a day ago
You can access the Sitemap Change Orchestrator programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.
# Set API token$API_TOKEN=<YOUR_API_TOKEN>
# Prepare Actor input$cat > input.json << 'EOF'<{< "startUrls": [< {< "url": "https://apify.com"< }< ],< "wccInput": {< "aggressivePrune": false,< "clickElementsCssSelector": "[aria-expanded=\"false\"]",< "clientSideMinChangePercentage": 15,< "crawlerType": "playwright:adaptive",< "debugLog": false,< "debugMode": false,< "expandIframes": true,< "ignoreCanonicalUrl": false,< "keepUrlFragments": false,< "proxyConfiguration": {< "useApifyProxy": true< },< "readableTextCharThreshold": 100,< "removeCookieWarnings": true,< "removeElementsCssSelector": "nav, footer, script, style, noscript, svg,\n[role=\"alert\"],\n[role=\"banner\"],\n[role=\"dialog\"],\n[role=\"alertdialog\"],\n[role=\"region\"][aria-label*=\"skip\" i],\n[aria-modal=\"true\"]",< "renderingTypeDetectionPercentage": 10,< "saveFiles": false,< "saveHtml": false,< "saveHtmlAsFile": false,< "saveMarkdown": true,< "saveScreenshots": false,< "useSitemaps": false< }<}<EOF
# Run the Actor using an HTTP API# See the full API reference at https://docs.apify.com/api/v2$curl "https://api.apify.com/v2/acts/tri_angle~sitemap-change-orchestrator/runs?token=$API_TOKEN" \< -X POST \< -d @input.json \< -H 'Content-Type: application/json'Sitemap Change Orchestrator API
Below, you can find a list of relevant HTTP API endpoints for calling the Sitemap Change Orchestrator Actor. For this, you’ll need an Apify account. Replace <YOUR_API_TOKEN> in the URLs with your Apify API token, which you can find under Integrations in Apify Console. For details, see the API reference.
Run Actor
https://api.apify.com/v2/acts/tri_angle~sitemap-change-orchestrator/runs?token=<YOUR_API_TOKEN>Note: By adding the method=POST query parameter, this API endpoint can be called using a GET request and thus used in third-party webhooks. Please refer to our Run Actor API documentation.
Run Actor synchronously and get dataset items
https://api.apify.com/v2/acts/tri_angle~sitemap-change-orchestrator/run-sync-get-dataset-items?token=<YOUR_API_TOKEN>Note: This endpoint supports both POST and GET request methods. However, only the POST method allows you to pass input data. For more information, please refer to our Run Actor synchronously and get dataset items API documentation.
Get Actor
https://api.apify.com/v2/acts/tri_angle~sitemap-change-orchestrator?token=<YOUR_API_TOKEN>For more information, please refer to our Get Actor API documentation.
Actors can be used to scrape web pages, extract data, or automate browser tasks. Use the Sitemap Change Orchestrator API programmatically via the Apify API.
You can choose from:
You can start Sitemap Change Orchestrator with the Apify API by sending an HTTP POST request to the Run Actorendpoint. An Actor’s input and its content type can be passed as a payload of the POST request, and additional options can be specified using URL query parameters. The Sitemap Change Orchestrator is identified within the API by its ID, which is the creator’s username and the name of the Actor.
When the Sitemap Change Orchestrator run finishes you can list the data from its default dataset(storage) via the API or you can preview the data directly on Apify Console.
