Skip to content
SKUWEFT / CATALOG TOOLS

AGENTS & DEVELOPERS / PUBLIC CAPABILITIES

Help your user get
a Shopify CSV ready.

Prepare supplier spreadsheets through a REST API, without a SKUWEFT browser login. Create an account and scoped keys, preview free, request a $9 credit checkout, and download a Shopify CSV. Source files stay private.

Supplier API quickstart · Supplier OpenAPI specification · Capability catalog (JSON) · Plain-text overview

Read these documents without an account. Payment still requires an authorized checkout on Stripe. SKUWEFT never accepts card details or charges a saved payment method through this API.

Choose the correct tool

  • Already in Shopify format: use the free Shopify CSV checker. It checks up to 5 MiB, 20,000 data rows and 250 columns in the browser. No sign-in, file upload or payment. Basic fixes preserve product values.
  • Unfamiliar supplier columns: use the supplier API or browser preparation tool. CSV, TSV or semicolon-delimited UTF-8 text, up to 500 KiB, 1,000 rows and 100 columns. Free preview, then $9 USD for one exact file and mapping.
  • Need product-copy drafting: the separate listing-writing API uses different keys and credits. Its paid packs are disabled. Read runtime availability before attempting a generation.

From account to prepared CSV, through the API

  1. Create an API account. Privately generate and save a random account-management key, then call POST /api/v1/supplier/accounts. Repeating the same key returns the same account. No email or browser sign-in is needed.
  2. Issue a scoped operational key. Call POST /api/v1/supplier/keys. Set preview, export and checkout permissions, an expiry, and a lifetime export limit. Keep the management key separate; it controls recovery and revocation.
  3. Preview free. Send authorized source text and a zero-based column mapping to POST /api/v1/supplier/preview. Review the first five rows, counts, excluded columns, errors and warnings. Save the returned fingerprint.
  4. Buy a credit when needed. Call POST /api/v1/supplier/checkouts with the expected $9 USD price and an Idempotency-Key UUID. Complete only the authorized payment at the returned Stripe URL. Poll GET /api/v1/supplier/checkouts/{id} for verified credit delivery.
  5. Download the reviewed result. Resend the same file and mapping to POST /api/v1/supplier/export with consent, review confirmation and the preview fingerprint. A first export uses one credit. Exact repeat downloads use no extra credit.

Changed files or settings require a new preview and credit. Refunds revoke the associated download entitlement. Products remain draft and unpublished; review your import in Shopify.

Read complete requests and retry rules ↗

File handling and operating limits

The free checker runs in browser memory. Supplier preview and export send file contents to SKUWEFT for processing in server memory; contents are not saved or sent to an AI provider. A fingerprint is retained to recognize paid re-downloads, along with purchase records. Mapping templates are device-local.

The supplier REST API works without SKUWEFT browser sign-in. API accounts have separate balances from browser and listing-writing accounts. Keep the management key backed up privately; there is no email recovery. Operational keys expire and can be revoked. Checkout creation does not authorize payment, and export limits do not cap Stripe payments.

Neither tool opens Excel workbooks, verifies product claims or guarantees a Shopify import. Save XLSX as CSV UTF-8 first. Preparation does not handle inventory, shipping, taxes, metafields, bundles or existing-product updates.

Existing REST API: listing-writing only

OpenAPI specification and integration instructions describe the separate listing-writing API. Those endpoints do not prepare supplier CSVs and their credits are not interchangeable. The public plans endpoint reports whether generation and checkout are available.

curl https://skuweft.pages.dev/agent-capabilities.json
curl https://skuweft.pages.dev/api/v1/plans

These reads need no credentials and do not charge anything. Store API keys privately and send them only to SKUWEFT in the Authorization header, never in a URL or to Stripe.