# Blibli Drop-shipper Data Sync (`zucchini_gopher_m2v/blibli-dropshipper-sync`) Actor

Keep your reseller catalogue accurate: bulk-check Blibli prices, stock and descriptions for the SKUs you sell, and get exactly what changed since the last run - price moves, stock flips and removed listings. No login needed.

- **URL**: https://apify.com/zucchini\_gopher\_m2v/blibli-dropshipper-sync.md
- **Developed by:** [Faisal Ahdan naufal](https://apify.com/zucchini_gopher_m2v) (community)
- **Categories:** E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.50 / 1,000 product rows

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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

## Blibli Drop-shipper Data Sync

Keep your reseller catalogue accurate. Give it the Blibli SKUs you sell and
it returns the **current price, availability, stock and description** — plus
**exactly what changed since the last run**, so you push updates instead of
re-importing everything.

Built for dropshippers reselling Blibli stock on their own store, Shopee,
Tokopedia, TikTok Shop or a webshop.

No login, no API key. HTTP-only — no browser.

### What it's actually for

Run it on a schedule. Each run tells you, per SKU:

| `changeType` | What you do in your store |
| --- | --- |
| `PRICE_INCREASED` / `PRICE_DECREASED` | Reprice — `changes.price` has from/to and `deltaPercent` |
| `OUT_OF_STOCK` | Pause or hide the listing |
| `BACK_IN_STOCK` | Re-activate it |
| `NAME_CHANGED` | Update your title |
| `BECAME_UNAVAILABLE` | The listing is gone — unpublish |
| `NEW` | First time seen |
| `UNCHANGED` | Nothing to do |

Set `onlyChangedItems: true` and the dataset contains **only the rows you
need to act on** — often a handful out of hundreds.

```json
{
  "sku": "BLL-70058-00122",
  "syncStatus": "OK",
  "name": "SanDisk Ultra microSDXC 64GB C10 UHS-I Card 100MB/s",
  "price": 255000,
  "listPrice": 299000,
  "discountPercent": 15,
  "inStock": true,
  "stockQuantity": 96,
  "changeType": ["PRICE_DECREASED"],
  "changes": { "price": { "from": 299000, "to": 255000, "deltaPercent": -14.72 } },
  "hasChanged": true
}
```

### Input

```json
{
  "productUrls": ["BLL-70058-00122", "COP-60023-00933"],
  "detailedMode": false,
  "trackChanges": true,
  "onlyChangedItems": true
}
```

`productUrls` takes bare SKUs or full product URLs — mix freely. You only
need to store SKUs; the actor reaches any product from its SKU alone.

| Field | Description |
| --- | --- |
| `detailedMode` | Off: bulk lookup, **1 request per 50 SKUs**, gives price + in-stock boolean. On: opens each product page for **exact stock quantity**, description, warranty, categories and all images — 1 request per SKU |
| `verifyMissing` | Re-check missing SKUs on their product page before calling them gone. **Leave this on** — see below |
| `trackChanges` | Compare against the previous run and label each SKU |
| `onlyChangedItems` | Emit only rows that changed |
| `stateStoreName` | Named store holding the snapshot; use one per catalogue |
| `proxyConfiguration` | Residential + country `ID` recommended for scheduled syncs |

### Why `verifyMissing` matters

Blibli's bulk endpoint **silently omits some products that are perfectly
alive.** Verified during recon: SKU `VAM-43292-00654` returns nothing from
the bulk endpoint while its product page shows a buyable listing with stock
6, and search reports it as `AVAILABLE`.

If the actor treated "missing from bulk" as "delisted", it would tell you to
unpublish products that are still selling. So every missing SKU is
re-checked against its product page before being reported as `NOT_FOUND`.
If you switch verification off for speed, those rows say explicitly in
`_errorDetail` that the absence was **not** confirmed.

### Suggested setup

- **Price/stock sync, 2–4× daily**: `detailedMode: false`,
  `onlyChangedItems: true`. A 500-SKU catalogue is ~10 requests.
- **Full content refresh, weekly**: `detailedMode: true`,
  `onlyChangedItems: false` — pulls descriptions, warranty and stock levels
  for rewriting listings.

### Known limits

- **Fast mode gives an in-stock boolean, not a quantity.** Exact stock needs
  `detailedMode`, at one request per SKU.
- **Variants are flagged but not enumerated** — `hasVariants` tells you a
  listing has options, but price and stock describe the default variant.
- A run is a point-in-time snapshot; freshness is whatever your schedule is.
- Descriptions are in Indonesian, as Blibli publishes them.

### Reliability

Blibli sits behind Cloudflare. The actor clears it HTTP-only with TLS
impersonation plus the required `Referer`, retrying with exponential backoff
and rotating both fingerprint and (with a proxy) egress IP on a block. A
failing SKU never sinks the run — it becomes a row with `_error` and
`_errorDetail` while the rest continue.

SKUs absent from a given run are carried forward in the snapshot rather than
dropped, so syncing part of your catalogue does not erase the rest of its
change history.

See [CRAWLING\_METHOD.md](CRAWLING_METHOD.md) for the endpoint evidence, the
field-by-field comparison of the two modes, and the silent-omission finding.

# Actor input Schema

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

The Blibli products in your catalogue, as full product URLs (https://www.blibli.com/p/<name>/ps--COP-60023-00933) or bare SKUs (COP-60023-00933). Resolved in bulk - 50 SKUs per request - so a large catalogue stays cheap to sync.

## `detailedMode` (type: `boolean`):

Open each product page instead of using the bulk endpoint. Adds exact stock QUANTITY, the cleaned product description, warranty text, categories and all images - but costs one request per SKU instead of one per 50. Use fast mode for frequent price/availability syncs and detailed mode when you also need copy and stock levels.

## `verifyMissing` (type: `boolean`):

STRONGLY RECOMMENDED. Blibli's bulk endpoint silently omits some products that are actually live and buyable, so an omission alone does not mean the listing is gone. With this on, every missing SKU is re-checked on its product page before being reported as NOT\_FOUND. Turning it off makes runs faster but risks telling you to unpublish products that are still on sale.

## `trackChanges` (type: `boolean`):

Compare this run against the previous one and label each product with what moved: PRICE\_INCREASED, PRICE\_DECREASED, OUT\_OF\_STOCK, BACK\_IN\_STOCK, NAME\_CHANGED, BECAME\_UNAVAILABLE, NEW or UNCHANGED. The snapshot is kept in a named key-value store so it survives between scheduled runs.

## `onlyChangedItems` (type: `boolean`):

Emit only products that actually changed since the last run - the smallest possible feed to push into your own store. Requires change tracking. On the first run everything counts as NEW.

## `stateStoreName` (type: `string`):

Named key-value store holding the previous snapshot. Use a different name per catalogue if you sync several stores independently.

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

Blibli is behind Cloudflare and throttles sustained traffic from one IP. Apify Residential proxy with country 'ID' is recommended for scheduled syncs.

## Actor input object example

```json
{
  "productUrls": [
    "BLL-70058-00122",
    "COP-60023-00933"
  ],
  "detailedMode": false,
  "verifyMissing": true,
  "trackChanges": true,
  "onlyChangedItems": false,
  "stateStoreName": "blibli-sync-state",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

Current product data plus per-SKU change detection.

# 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 = {
    "productUrls": [
        "BLL-70058-00122",
        "COP-60023-00933"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("zucchini_gopher_m2v/blibli-dropshipper-sync").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 = { "productUrls": [
        "BLL-70058-00122",
        "COP-60023-00933",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("zucchini_gopher_m2v/blibli-dropshipper-sync").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 '{
  "productUrls": [
    "BLL-70058-00122",
    "COP-60023-00933"
  ]
}' |
apify call zucchini_gopher_m2v/blibli-dropshipper-sync --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zucchini_gopher_m2v/blibli-dropshipper-sync"
        }
    }
}

```

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/17lKCwG3OYyfQ6bxw/builds/8YFuos6He4TTJm9cb/openapi.json