logo

API Reference

Complete reference for every MultiCartAPI endpoint. All requests go to the base URL below and authenticate with your API key. Pick a resource from the left, or read the essentials first.

Base URLhttps://multicartapi.com/api/v1

Authentication

Every authenticated endpoint accepts either of two interchangeable credentials. Send your API key as x-api-key, or a dashboard session token as Authorization: Token …. A handful of read-only endpoints (listing domains, Officeworks stores, and public plans) need no authentication at all.

The response envelope

Every endpoint returns HTTP 200 wrapped in a consistent envelope. Branch on status (1 = success, 0 = failure) rather than the HTTP status code; the intended HTTP code is carried in code.

Envelope
{
  "code": 200,        // intended HTTP code
  "data": { ... },    // payload on success, or an error message on failure
  "status": 1         // 1 = success, 0 = failure
}

Two streaming exceptions

The result-file download (/results/…) and invoice PDF endpoints return raw bytes, not the JSON envelope.

Response codes

CodeMeaning
200Success (status: 1).
400Bad request — missing/invalid parameter, or an unmet prerequisite (e.g. no cookie for the domain + postcode).
402Insufficient credits to run the request.
404Resource not found (unknown collection / ASIN / zipcode id).
409Conflict — duplicate (e.g. a postcode or ASIN that already exists).
500Unexpected server error.
503Temporarily unavailable / scraping backend busy.

Resources

Authentication & Account7Endpoints for authenticating users, reading and updating profile/account data, rotating API keys, and checking credit balances. All authenticated endpoints accept either a session token or an API key interchangeably.Registration & Password Reset4Public endpoints for creating a new account (two-step OTP verification then registration) and for resetting a forgotten password (OTP request then reset). All four endpoints require no authentication.Collections (Shared)9Collections are the container for scrape jobs. Each collection belongs to one supplier type (amazon or officeworks.com.au). All endpoints require authentication via API Key or Session Token.Amazon Items9CRUD operations for Amazon ASINs within a collection, plus bulk ingestion and scraped-output retrieval. All paths are under /api/v1/schedules/amazon/asin/. Legacy /schedules/asin/* aliases exist but are deprecated.Amazon Category3Scrape an entire Amazon category page by URL and browse node ID. Each call creates its own collection with request_type='amazon_category_scrape' and dispatches to a dedicated Celery queue. Currently filters (prime, delivery day) are supported on amazon.com.au only; a valid cookie file for the domain+postcode must exist before submitting.Officeworks Items7Manage Officeworks SKUs within a collection. SKUs are stored in the same underlying table as Amazon ASINs, with the SKU code in the `asin` field, store ID in `custom_id`, and domain hard-coded to `officeworks.com.au`.Officeworks Catalogue2Proxy endpoints that query the live Officeworks public catalogue — categories (cached 24 h server-side) and Algolia product search — without consuming scrape credits.Officeworks Stores1Public reference data for all active Officeworks store locations. No authentication is required — this endpoint is intentionally open so integrations can look up valid store IDs before creating collections or SKUs.Postcodes / Zipcodes5Postcodes are user-scoped and domain-scoped. For Amazon domains, creating a postcode triggers asynchronous cookie generation in a background thread; the record starts with status `in-progress` and becomes `active` once cookies are ready. For non-scraping domains (REST API / CSV import) the postcode is immediately set `active`.Playground2Synchronous one-shot scrapes for testing a single Amazon ASIN or Officeworks SKU. Each successful call consumes 1 credit. Results are returned immediately in the response body — no collection or runner polling required.Domains & Settings1Reference data endpoints for the platform's supported domains (suppliers). No authentication is required — these are public read-only resources used to discover valid domain IDs before creating zipcodes or items.Plans2Plan catalog endpoints for listing available subscription plans. Two public-facing endpoints are exposed: an authenticated listing used by the billing UI and an unauthenticated public catalog for the marketing site.