Skip to main content
POST
https://api-ai.textyess.com
/
products
/
bulk-update
Bulk Update Products
curl --request POST \
  --url https://api-ai.textyess.com/products/bulk-update \
  --header 'Content-Type: application/json' \
  --header 'x-auth-token: <api-key>' \
  --data '
{
  "products": [
    {
      "id": "<string>",
      "title": "<string>",
      "description": "<string>",
      "image": "<string>",
      "url": "<string>",
      "variants": [
        {
          "id": "<string>",
          "title": "<string>",
          "price": "<string>",
          "inventory_quantity": 123,
          "variant_url": "<string>"
        }
      ],
      "collections": [
        {}
      ]
    }
  ]
}
'
{
  "success": true,
  "message": "Products update queued successfully"
}

​
Overview

The bulk update endpoint allows you to modify multiple existing products in your catalog simultaneously. This is useful for updating prices, inventory, or product details in batch.

​
Authentication

This endpoint requires a valid JWT token in the x-auth-token header. You can find your token in the Developers section: 
x-auth-token: your_jwt_token

​
Body Parameters

​
products
array
required
Array of products to update. Only include the fields you want to modify - omitted fields will remain unchanged.

​
Response

​
success
boolean
Indicates if the update was successful
​
message
string
A human-readable message describing the result
{
  "success": true,
  "message": "Products update queued successfully"
}

​
Rate Limiting

You can call the bulk update endpoint up to 100 times per 5 minutes. After that will Exceeding this limit will make it impossible for you to make further calls to this endpoint for 3, 12 and finally 24 hours. If this limit is exceeded four times you will not be allowed to make calls to this endpoint indefinitely.

​
Best Practices

  1. Partial Updates: Only include fields that need to be updated - omitted fields will retain their current values.
  2. Batch Size: Keep batches under 500 products to avoid rate limits.
  3. Error Handling: Implement retry logic with exponential backoff for rate limit errors.
  4. Validation: Always include the product and variant IDs to ensure correct updates.
  5. Idempotency: The operation is not idempotent - sending the same update multiple times will cause issues.