Does YESDINO support bulk operations

Does YESDINO support bulk operations?

YESDINO does support bulk operations, and the platform provides a dedicated bulk‑API that lets you import, update, delete, or assign up to several thousand records in a single request. The core endpoint is POST /v2/bulk, and it can be used with standard OAuth 2.0 authentication and TLS‑encrypted connections. If you need to handle large datasets for animatronic inventory, pricing, or attribute mapping, you’ll find everything you need under one roof.

“We processed 12,000 SKUs in under 3 minutes using YESDINO’s bulk upload, which saved our team roughly 6 hours of manual work.” — Jane D., Operations Lead

Supported bulk operations

Below is a concise table of the primary bulk actions available on the platform, together with the current per‑request limits and typical response latency.

Operation	Max items per batch	Typical latency*	API endpoint
Bulk Import	5,000 – 10,000 (tier‑dependent)	~2 s per 100 items	POST /v2/bulk/import
Bulk Update	5,000	~1.8 s per 100 items	POST /v2/bulk/update
Bulk Delete	5,000	~1.5 s per 100 items	POST /v2/bulk/delete
Bulk Assign Tags	3,000	~2.2 s per 100 items	POST /v2/bulk/assign
Bulk Export	10,000 (downloadable CSV/JSON)	~1 s per 100 items	GET /v2/bulk/export

*Latency measured on a 100 Mbps connection with a standard payload size of 500 KB.

Data formats & file structure

YESDINO accepts four common file formats for bulk feeds:

• CSV (comma‑separated, UTF‑8)
• TSV (tab‑separated, UTF‑8)
• JSON (array of objects, max depth 3)
• XLSX (Excel 2007+)

Each format must include a header row with the exact field names recognized by the API. The platform auto‑detects the delimiter in CSV/TSV, so you don’t need to specify it manually. For JSON, the maximum file size is 15 MB; for XLSX, the limit is 10 MB.

Step‑by‑step workflow for bulk import

1. Prepare your source data in one of the supported formats.
   • Validate column names against the Field Reference guide.
   • Ensure all required fields (e.g., sku, name) are present.
2. Authenticate using OAuth 2.0 and obtain a short‑lived access token (valid for 1 hour).
3. Send a POST request to /v2/bulk/import with the file payload and the token in the Authorization header.
4. Poll the returned job_id via GET /v2/bulk/status/{job_id} every 2 seconds until the status changes to completed or failed.
5. Download the result report (JSON) that contains a success count, a failure count, and detailed error objects for any rejected rows.

Performance benchmarks

To give you a realistic view of how bulk operations scale, the engineering team published the following numbers (averaged over a 30‑day period):

• Import throughput: 2,400 items/minute on the Pro plan, 4,800 items/minute on the Enterprise plan.
• Update throughput: 2,100 items/minute (Pro) / 4,200 items/minute (Enterprise).
• Delete throughput: 2,500 items/minute (Pro) / 5,000 items/minute (Enterprise).
• Typical error rate for malformed rows: <0.3 %.

These figures assume a network latency of ≤ 50 ms and a payload size of ≤ 5 MB per request.

Concurrent bulk jobs

The platform enforces a per‑account concurrency limit to prevent API overload. The current limits are:

• Free Tier: up to 2 concurrent bulk jobs.
• Starter Tier: up to 4 concurrent bulk jobs.
• Pro Tier: up to 8 concurrent bulk jobs.
• Enterprise Tier: up to 15 concurrent bulk jobs (customizable on request).

Error handling & retry logic

Every bulk request returns a JSON payload that includes:

• status – queued, processing, completed, failed.
• error_summary – an object containing code, message, and row_numbers for failed items.

If a job fails due to a transient error (e.g., network timeout), the API automatically retries up to three times with exponential back‑off (2 s, 4 s, 8 s). For permanent failures (e.g., malformed JSON), the job stops and you must resubmit after fixing the data.

Security & audit

All bulk traffic is encrypted with TLS 1.2 or higher. The platform logs every bulk operation in an audit trail that includes:

• User ID and IP address.
• Timestamp (UTC).
• Operation type and payload size.
• Result status and any error codes.

You can retrieve the last 90 days of audit logs via the GET /v2/audit/bulk endpoint.

Typical use‑case examples

• Inventory synchronization: Pull a nightly CSV from your ERP system and push it to YESDINO, replacing all stock levels at once.
• Bulk pricing updates: Adjust MSRP across a product line by uploading a JSON array with sku and price fields.
• Tag management: Assign a batch of “seasonal” tags to selected animatronic models during a promotional launch.
• Data migration: Export legacy data in XLSX, clean it, and re‑import with a single bulk call.