Using storage_destination_id

Store rendered images in a storage bucket your organization controls.

How it works

The storage_destination_id parameter tells the API to save rendered files to a destination configured in the dashboard at https://htmlcsstoimage.com/dashboard/storage-destinations.

It works with:

• HTML/CSS image requests.
• URL screenshot requests.
• Image batches, as either a variation or a default option.
• Templates, where the destination is saved for images created from the template.

For provider setup, permissions, connection testing, and storage behavior, see the full Storage Destinations guide.

When you choose to Disable HCTI Storage, the image create response contains a /v1/store/... URL. Send an authenticated PUT request to that URL using valid API credentials from the same organization as the image. A 200 or 424 response reports the overall outcome and the status, target, bucket, and key for the base image and any transformation. See Store response for the full response format.

Value

Example usage

JSON request

{
  "html": "<h1>Saved in my bucket</h1>",
  "storage_destination_id": "your-storage-destination-id"
}

cURL

curl -X POST https://hcti.io/v1/image \
  -u 'UserID:APIKey' \
  -H 'Content-Type: application/json' \
  -d '{
        "url": "https://example.com",
        "storage_destination_id": "your-storage-destination-id"
      }'

Template

{
  "name": "Stored template",
  "html": "<h1>Saved in my bucket</h1>",
  "storage_destination_id": "your-storage-destination-id"
}

Need help?

Talk to a human. Please email us support@htmlcsstoimage.com with any questions and we’ll gladly help you get started.