---
title: "Olostep / Update batch metadata"
description: "Olostep tool olostep-batch-update on looot: input fields, $0 per call, output shape, and code to run it with curl, JavaScript or Python."
sidebar:
  hidden: true
---

{/* Generated by scripts/generate-api-reference.mjs from data/api-reference.json. Do not edit. */}

:::warning
This tool is a write action: it changes data in your account at the provider, not only reads it. Run it on purpose, with the input you mean.
:::

Write action: this changes state on looot's Olostep account. Updates the metadata for a specific batch. Only the `metadata` field can be updated. Follows Stripe's merge semantics: new keys are added, existing keys are updated, and keys set to empty string are deleted.

- **Tool id:** `olostep-batch-update`
- **Provider:** [Olostep](/providers/olostep)
- **Job:** [Update web scrape batch](/reference/jobs/web-scrape-batch-update) (`web.scrape.batch.update`)
- **Price:** $0 per call. A call that fails at the provider costs $0.

## Inputs

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `metadata` | object | yes | Set of key-value pairs for storing additional information about an object. Follows Stripe's approach with validation rules: max 50 keys, key max 40 characters (no square brackets), value max 500 characters, all values stored as strings. |
| `batch_id` | string | yes | The ID of the batch to update. |

## Output

The run's `result` holds the provider's answer. Signed in, `looot inspect olostep-batch-update` prints its fields.

## Run it

Every call needs your API token in `LOOOT_TOKEN`; [Sign in](/get-started/sign-in#use-the-token-in-scripts-and-agents) shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With `wait: 30` the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll `GET /v1/runs/<runId>`.

Example input with placeholder values:

<CodeGroup>

```bash curl
curl -X POST "https://api.looot.ai/v1/runs" \
  -H "Authorization: Bearer $LOOOT_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"endpointId":"olostep-batch-update","input":{"batch_id":"<batch_id>","metadata":{}},"wait":30}'
```

```js JavaScript
const response = await fetch("https://api.looot.ai/v1/runs", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
    "Content-Type": "application/json",
    "Idempotency-Key": crypto.randomUUID(),
  },
  body: JSON.stringify({
    endpointId: "olostep-batch-update",
    input: {
      batch_id: "<batch_id>",
      metadata: {},
    },
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);
```

```python Python
import os
import uuid

import requests

response = requests.post(
    "https://api.looot.ai/v1/runs",
    headers={
        "Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "endpointId": "olostep-batch-update",
        "input": {
            "batch_id": "<batch_id>",
            "metadata": {},
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))
```

</CodeGroup>

To let looot pick among every provider of this job instead, send `job:web.scrape.batch.update` as `endpointId`; see [the job page](/reference/jobs/web-scrape-batch-update).
