# Store Get

Look up the public Iceland store directory and check published delivery eligibility for a supplied postcode.

- Platform: [Iceland](https://docs.upscrape.com/docs/platforms/iceland)
- Capability ID: `iceland.store.get`
- Cost: 1 credit per request
- Maximum runtime: 30 seconds
- Execute endpoint: `POST https://data.upscrape.com/execute`

## Request

Use the exact public capability ID in the shared execute envelope.

```bash
curl --request POST \
  --url https://data.upscrape.com/execute \
  --header "Authorization: Bearer $UPSCRAPE_API_KEY" \
  --header "Content-Type: application/json" \
  --header "Prefer: wait=30" \
  --data '{
  "input": {
    "postcode": "CH5 2NW",
    "store_id": "114"
  },
  "capability": "iceland.store.get"
}'
```

## Input

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `postcode` | `string` | No |  |
| `store_id` | `string` | No | Store identifier. |

### Example input

```json
{
  "postcode": "CH5 2NW",
  "store_id": "114"
}
```

## Response

Successful output is returned in `results[0].data`. Raw platform output is intentionally open-ended and may evolve with the upstream source.

### Illustrative sample output

This redacted fixture is an example, not a fixed response schema.

```json
{
  "delivery_area": {
    "deliverable": true,
    "nearest_store": null,
    "postcode": "CH5 2NW"
  },
  "items": [
    {
      "id": "114",
      "name": "ABERDARE"
    }
  ],
  "total": 1
}
```
### Illustrative output fields

Derived from the sample above for orientation only. These fields are not a fixed response schema.

| Path | Observed type | Example |
| --- | --- | --- |
| `delivery_area` | `object` | 3 fields |
| `delivery_area.deliverable` | `boolean` | true |
| `delivery_area.nearest_store` | `null` | null |
| `delivery_area.postcode` | `string` | CH5 2NW |
| `items` | `array` | 1 items |
| `items` | `array` | 1 items |
| `total` | `integer` | 1 |

## Execution behavior

A `200` response completed inline. A `202` response was queued; poll `GET /jobs/{id}` until the job reaches `completed` or `failed`. Use an `Idempotency-Key` when retrying must not create a duplicate logical job.

## Related documentation

- [Authentication](https://docs.upscrape.com/docs/api/authentication)
- [Jobs and results](https://docs.upscrape.com/docs/api/jobs)
- [Errors and retries](https://docs.upscrape.com/docs/api/errors)
- [Idempotency](https://docs.upscrape.com/docs/api/idempotency)