Supplier Availability API

Track Supplier/manufacturer public product pages, Public sitemaps/RSS/CSV/XML feeds, Apify Standby mode and return product availability, price, stock, review, catalog, and change records.

Who this is for

Commercial, revenue, procurement, ecommerce, product, and supplier operations teams use this actor when they need focused supplier availability output instead of a broad generic scraper or manual checking.

Buyer outcomes

• Track supplier availability changes without manually checking supplier, catalog, app, or marketplace pages.
• Prioritize action with previous/current values, availability, price, stock, review, listing, confidence, and source URL.
• Route change records into commercial, revenue, ecommerce, purchasing, or operations workflows.

Sources monitored

• Supplier/manufacturer public product pages
• Public sitemaps/RSS/CSV/XML feeds
• Apify Standby mode

Inputs

• sourceMode: use sample for a smoke run or startUrls for supplier/product/app listing URLs.
• startUrls: product, SKU, supplier, catalog, app marketplace, pricing, stock, or review URLs.
• sourceIds: approved supplier, marketplace, or catalog source identifiers.
• maxItems: bounded number of products, SKUs, listings, or changes to return.
• sinceLastRun: emit only new or changed product/listing states when scheduled.
• watchlistTerms: SKU, product, brand, vendor, app, price, stock, or availability terms.
• webhookUrl: optional destination for price, stock, availability, or review-change alerts.

How it transforms the input

• Input: supplier, SKU, product, app listing, catalog, review, stock, or pricing URL.
• Transformation: compare the current observed state with prior run data or configured expectations.
• Output: product identifier, supplier/source URL, previous/current price, availability, stock signal, change type, timestamp, and confidence.

Outputs

The actor returns supplier/product/listing change records with product identifiers, source URLs, price and stock state, availability, change type, timestamps, and confidence.

Family-specific fields to expect:

• productUrl: Supplier, SKU, product, catalog, app, or listing URL.

• sku: Supplier SKU or product identifier.

• productName: Product or listing name.

• price: Current observed price.

• currency: Currency for price fields.

• availability: Availability state from the source.

• stockStatus: In-stock, out-of-stock, limited, preorder, or unknown state.

• previousPrice: Previous observed price when change tracking is available.

• priceChange: Absolute or relative price movement.

• detectedAt: Timestamp when the change was detected.

• recordId: Stable record ID for exports, dedupe, and downstream joins.

• title: Human-readable record title for review and export.

• sourceName: Source identifier used to trace where the record came from.

• sourceUrl: Direct source URL for review and audit.

• dedupeKey: Stable key used for delta mode and duplicate suppression.

• retrievedAt: Timestamp showing when the actor retrieved or generated this record.

• score: Normalized field for filtering, routing, or downstream review.

• scoreReasons: Buyer-readable explanation for the score or match.

• confidence: Normalized field for filtering, routing, or downstream review.

• errors: Normalized field for filtering, routing, or downstream review.

• runSummary: Run-level summary for counts, filters, charges, and next actions.

Pricing

This actor uses Apify pay-per-event pricing. Current public listing guidance: $29-$49 / 1,000 launch validation records until public data proof is complete. Charges are tied to buyer-visible value events such as lookup-result, dataset-processed, record-saved, enriched-record. Small validation runs are supported so you can inspect output before scaling a schedule.

• lookup-result: Charge when Supplier Availability API produces Lookup Result. Typical price: $0.043. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• dataset-processed: Base charge when Supplier Availability API writes a non-empty default dataset. Typical price: $0.011. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• record-saved: Charge for each buyer-visible result saved by Supplier Availability API. Typical price: $0.003. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• enriched-record: Charge when Supplier Availability API adds match scoring, source evidence, or enrichment to a saved result. Typical price: $0.022. A run that produces 10 matching records charges only for the matched buyer-value events and remains capped by the run limit.
• first-run-cap: Recommended first run budget cap. Typical price: $3.820. Start with the default small run, inspect the dataset, then raise maxItems or schedule recurring runs.

API example

curl -X POST "https://api.apify.com/v2/actors/zentrafoundry~supplier-availability-api/runs" \
+  -H "Authorization: Bearer $APIFY_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"maxItems":10,"sourceIds":["SUPPLIER-PUBLIC","SITEMAPS-RSS","APIFY-STANDBY"],"includeSourceUrls":true,"includeMatchReasons":true,"outputMode":"buyer-ready-records"}'

Recommended first run

{
    "maxItems": 10,
    "sourceIds": [
        "SUPPLIER-PUBLIC",
        "SITEMAPS-RSS",
        "APIFY-STANDBY"
    ],
    "includeSourceUrls": true,
    "includeMatchReasons": true,
    "outputMode": "buyer-ready-records"
}

Sample output

Sample status: sample_unavailable at https://zentra.nimblique.studio/external/actor-review/samples/supplier-availability-api.json. No fake sample is published; run a bounded real sample refresh before using examples in promotion.

Recommended public tasks

[
    {
        "name": "Check 10 product/listing changes",
        "description": "Low-cost validation run for checking product, SKU, price, stock, and availability fields.",
        "input": {
            "maxItems": 10,
            "sourceIds": [
                "SUPPLIER-PUBLIC",
                "SITEMAPS-RSS",
                "APIFY-STANDBY"
            ],
            "includeSourceUrls": true,
            "includeMatchReasons": true,
            "outputMode": "buyer-ready-records",
            "actorSlug": "supplier-availability-api"
        }
    },
    {
        "name": "Daily supplier change check",
        "description": "Recurring batch for price, stock, catalog, review, or marketplace changes.",
        "schedule": "Daily during local business hours",
        "input": {
            "maxItems": 25,
            "sourceIds": [
                "SUPPLIER-PUBLIC",
                "SITEMAPS-RSS",
                "APIFY-STANDBY"
            ],
            "includeSourceUrls": true,
            "includeMatchReasons": true,
            "outputMode": "buyer-ready-records",
            "actorSlug": "supplier-availability-api"
        }
    }
]

Use cases

• Track supplier availability availability, price, stock, review, or marketplace position changes.
• Send product or app listing changes into commercial, revenue, or operations workflows.
• Compare current and previous values with source evidence and confidence.
• Schedule recurring checks for supplier/catalog drift.

Trust and compliance

• Uses Supplier/manufacturer public product pages, Public sitemaps/RSS/CSV/XML feeds, Apify Standby mode.
• Keeps source URLs and source identifiers in output records for auditability.
• Does not require private credentials unless a source is explicitly configured for approved authenticated access.

Limitations

• Results depend on public-source availability, source uptime, and source update cadence.
• Public sources can revise records after publication; rerun scheduled tasks for fresh evidence.
• Scores and match reasons are decision-support signals, not legal, financial, procurement, medical, safety, or regulatory advice.
• Large production runs can cost more than the default smoke run; start small, inspect output, then scale schedules.

FAQ

Can I run this without URLs? Yes. The default sample mode is designed to succeed without user-supplied URLs, and URL-backed runs can use startUrls when needed.

Can I schedule it? Yes. Use sinceLastRun, watchlistTerms, and optional webhookUrl to turn the actor into a recurring alert or report workflow.

How do I verify value before scaling? Run the recommended first-run input, review the sample output fields, then increase maxItems or schedule recurring runs after the dataset matches your use case.