# Amazon Delivery & Availability Check (`cyprusapi/amazon-delivery-availability`) Actor

Delivery promise/date, shipping cost, availability and Buy Box price per ASIN at a chosen delivery location (postal code or city) across 18 Amazon marketplaces. Pay per delivered answer, errors never charged.

- **URL**: https://apify.com/cyprusapi/amazon-delivery-availability.md
- **Developed by:** [Torchtechnology LTD](https://apify.com/cyprusapi) (community)
- **Categories:** E-commerce, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 availability checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### What does this Actor do?

Amazon Delivery & Availability Check answers the question shoppers actually care about: **"When would this product arrive at MY address, and what does shipping cost?"** Give it ASINs (or product URLs), a marketplace, and a delivery location — a **postal code** or **city** — and it sets that location on Amazon (anonymously, via Amazon's own location selector, once per run) and then reads every product page *at that location*: **delivery promise/date, order-within cutoff, shipping cost, stock availability, and the Buy Box price/seller**. Works across **18 Amazon marketplaces**.

Delivery promises on Amazon are location-dependent — the same ASIN shows different dates, shipping fees, and even stock status for Berlin 10115 vs. Munich 80331. This Actor captures exactly what a buyer at the requested location would see.

### Why this Actor?

- **True location-aware answers** — the location is really set in the Amazon session (not guessed), and the Actor reads back Amazon's own confirmation. If the requested location did not stick, the item says so and is **not charged**.
- **18 marketplaces with verified location UIs** — Amazon's location modal is different per marketplace: single postcode input (de, com, co.uk, fr, it, es, in, mx), two-part postcode fields (ca, co.jp, se, pl, br), postcode + suburb picker (com.au), city typeahead (ae), city dropdown (sa). All handled, all live-verified.
- **Honest billing** — you pay one `availability` event per ASIN with a delivered location answer. Errors, blocks, not-found ASINs, and locations Amazon rejected are pushed as transparency items and **never charged**.
- **Batch-friendly** — the location is applied once per run; dozens of ASINs share the session.

### How to use

1. Provide `asins` (10-character Amazon IDs) and/or `productUrls` (`/dp/…` or `/gp/product/…` links).
2. Pick the `marketplace` (default: `de`).
3. Set `postalCode` matching the marketplace (e.g. `10115` for de, `10001` for com, `SW1A 1AA` for co.uk) — or `city` for ae/sa (e.g. `Dubai`, `Riyadh`). Skip both to get answers for Amazon's geo-detected location.
4. Run. One dataset item per ASIN.

```json
{
  "asins": ["B0BLGJTJRD", "B00008XF6W"],
  "marketplace": "de",
  "postalCode": "10115"
}
```

### Input reference

| Field | Type | Default | Description |
|---|---|---|---|
| `asins` | string\[] | — | ASINs to check (batch freely) |
| `productUrls` | string\[] | — | Amazon product URLs; the ASIN is extracted |
| `marketplace` | string | `de` | One of 18: de, com, co.uk, fr, it, es, ca, com.au, co.jp, in, nl, se, pl, be, mx, br, ae, sa |
| `postalCode` | string | — | Delivery postal code, format matching the marketplace (`10115`, `10001`, `SW1A 1AA`, `M5V 3L9`, `100-0001`, `00-950`, `01310-100`, …) |
| `city` | string | — | Delivery city for ae/sa (`Dubai`, `Riyadh`). Ignored when `postalCode` is set |
| `maxItems` | integer | `5` | Upper bound of ASIN items per run |
| `proxyConfiguration` | object | Apify Residential | Proxy settings; custom `proxyUrls` supported |
| `proxiesByMarketplace` | object | — | Geo-pinned proxies per marketplace — tried first, ahead of the bundled pool and the Apify tiers |

### Output

One dataset item per ASIN. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

```json
{
  "asin": "B00008XF6W",
  "marketplace": "de",
  "title": "AMAZON GIFT CARD …",
  "locationRequested": "10115",
  "locationType": "postal",
  "locationApplied": true,
  "appliedLocation": "10115 Berlin",
  "deliveryTime": "Freitag, 21. August",
  "deliveryCutoff": "Bestelle innerhalb 5 Stunden 12 Minuten",
  "shippingText": "GRATIS",
  "shippingFree": true,
  "deliveryMessages": [
    {
      "message": "GRATIS Lieferung Freitag, 21. August …",
      "deliveryTime": "Freitag, 21. August",
      "deliveryPrice": "GRATIS",
      "deliveryType": "Default",
      "deliveryCutoff": "Bestelle innerhalb …",
      "shippingFree": true
    }
  ],
  "availabilityText": "Auf Lager",
  "inStock": true,
  "hasFeaturedOffer": true,
  "buyboxPrice": {"value": 7.49, "currency": "EUR"},
  "buyboxSellerName": "Example Seller",
  "buyboxFulfilledBy": "Amazon",
  "currency": "EUR",
  "scrapedAt": "2026-08-18T09:00:00Z"
}
```

| Field | Meaning |
|---|---|
| `locationRequested` / `locationType` | What you asked for |
| `locationApplied` | `true` only when Amazon's own confirmation/ingress echoes the requested location |
| `appliedLocation` | The location Amazon actually used (from the page's own evidence) |
| `locationNote` | Why a location did not apply (rejected, UI changed, marketplace has no anonymous setting) |
| `deliveryTime` / `deliveryCutoff` / `deliveryType` | Typed delivery promise from Amazon's `data-csa-c-delivery-*` attributes (language-independent) |
| `shippingText` / `shippingFree` | Shipping cost as shown + parsed free-shipping flag |
| `deliveryMessages` | All rendered delivery slots (fastest first), raw text + typed attributes |
| `availabilityText` / `inStock` | Stock status (tri-state: `true` / `false` / `null` unknown) |
| `buyboxPrice` / `buyboxSellerName` / `buyboxFulfilledBy` | Buy Box at that location |
| `error` / `errorDescription` | Transparency items (`invalid_input`, `not_found`, `blocked`, `transport`) — never charged |

`RUN_SUMMARY` (key-value store) aggregates counts, the run's location, and charged events.

### Marketplace location support

| Marketplaces | Location input |
|---|---|
| de, com, co.uk, fr, it, es, in, mx | postal code |
| ca, co.jp, se, pl, br | postal code (two-part format ok, e.g. `M5V 3L9`, `100-0001`) |
| com.au | postal code (suburb is auto-picked) |
| ae, sa | city (`Dubai`, `Riyadh`, …) |
| nl, be | **no anonymous setting** — Amazon requires sign-in; the Actor reports the geo-detected location with `locationApplied: false` (not charged when a location was requested) |

### Pricing

Pay per **delivered answer** (`availability` event): one charge per ASIN where the location-based answer was actually read and pushed. Blocked pages, transport errors, not-found ASINs, invalid input, and rejected locations are **never charged** — they appear as transparency items instead. See the Pricing tab for the current price.

### Tips

- **Batch ASINs per run** — the location is set once per session, so 20 ASINs at one location cost barely more time than 5.
- Use residential proxies with an exit country matching the marketplace (the bundled pool does this; `proxiesByMarketplace` always wins if you bring your own).
- Proxy tier chain per task: your `proxiesByMarketplace` pool first, then the bundled pool (per-Actor named KVS `proxy-pool-amazon-delivery-availability`, record `pool`), then Apify datacenter, then Apify residential. Retries only on blocks/transport errors, each on a fresh session with the location re-applied.

### FAQ & limitations

- **nl/be:** Amazon shows anonymous users no location control (sign-in only) — answers reflect the proxy exit's geo location and are reported as such.
- Postcode formats must match the marketplace (`SW1A 1AA` on co.uk, not `SW1A1AA`-only variants may also work; `00-950` on pl). Amazon's own validation errors are reported in `locationNote`.
- Delivery dates are what Amazon renders at run time, in the marketplace's language.
- **Legality:** this Actor reads publicly visible shopping information. Comply with Amazon's ToS and applicable law.
- Issues tab is open — marketplace/selector maintenance is part of the product.

### Use with AI agents (MCP)

Actor identity: `cyprusapi/amazon-delivery-availability`. Tool description: check Amazon delivery date, shipping cost, stock and Buy Box price per ASIN at a chosen delivery location (postal code or city) across 18 marketplaces.

> Example prompt: "Would B0BLGJTJRD arrive this week at Munich 80331 and what does shipping cost?" → input: `{"asins": ["B0BLGJTJRD"], "marketplace": "de", "postalCode": "80331"}`

Pairs naturally with **cyprusapi/amazon-price-buybox** (full offer lists) and **cyprusapi/amazon-product** (full product data incl. GPSR).

# Actor input Schema

## `asins` (type: `array`):

Amazon ASINs (10 characters) to check, e.g. B0BLGJTJRD. One dataset item per ASIN. Provide asins and/or productUrls.

## `productUrls` (type: `array`):

Amazon product URLs (/dp/... or /gp/product/...). The ASIN is extracted from each URL; the run's marketplace setting decides which Amazon domain is fetched. Provide asins and/or productUrls.

## `marketplace` (type: `string`):

Amazon marketplace all ASINs are checked on (domain, locale, currency, and price-parsing logic follow this setting).

## `postalCode` (type: `string`):

Delivery postal code to set before checking (e.g. 10115 for de, 10001 for com, SW1A 1AA for co.uk, M5V 3L9 for ca, 100-0001 for co.jp). The location is applied once per run via Amazon's location selector and kept for all ASINs. Use `city` instead for ae/sa, which pick the location by city. nl/be offer no anonymous location setting (sign-in only) — answers there reflect the geo-detected location. If neither is given, answers reflect Amazon's geo-detected location.

## `city` (type: `string`):

Delivery city for marketplaces that pick the location by city instead of postal code (ae: e.g. Dubai; sa: e.g. Riyadh). Ignored when postalCode is set.

## `maxItems` (type: `integer`):

Upper bound of ASIN items pushed in this run.

## `proxyConfiguration` (type: `object`):

Residential proxies are strongly recommended. Custom proxies can be added as proxyUrls (http://user:pass@host:port).

## `proxiesByMarketplace` (type: `object`):

Optional: {"de": \["http://user:pass@host:port", …], "co.uk": \[…]}. Geo-pinned proxies per marketplace — exit-IP country should match the marketplace, otherwise Amazon serves wrong currencies or bot-gates. Proxy tier chain per task: this explicit pool FIRST; otherwise the bundled shared pool (we cover it); on blocked/transport the run falls back to Apify datacenter, then Apify residential. With useApifyProxy off and no pool at all: single direct attempt.

## Actor input object example

```json
{
  "asins": [
    "B0BLGJTJRD"
  ],
  "productUrls": [
    "https://www.amazon.de/dp/B0BLGJTJRD"
  ],
  "marketplace": "de",
  "postalCode": "10115",
  "maxItems": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "asins": [
        "B0BLGJTJRD"
    ],
    "productUrls": [
        "https://www.amazon.de/dp/B0BLGJTJRD"
    ],
    "postalCode": "10115"
};

// Run the Actor and wait for it to finish
const run = await client.actor("cyprusapi/amazon-delivery-availability").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "asins": ["B0BLGJTJRD"],
    "productUrls": ["https://www.amazon.de/dp/B0BLGJTJRD"],
    "postalCode": "10115",
}

# Run the Actor and wait for it to finish
run = client.actor("cyprusapi/amazon-delivery-availability").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "asins": [
    "B0BLGJTJRD"
  ],
  "productUrls": [
    "https://www.amazon.de/dp/B0BLGJTJRD"
  ],
  "postalCode": "10115"
}' |
apify call cyprusapi/amazon-delivery-availability --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,cyprusapi/amazon-delivery-availability"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/wp2knPdjSdIjU3nE2/builds/H7gRBVl03skdvoZ62/openapi.json