Destroys an asset or resource
Basic authentication using Cloudinary API Key and API Secret.
In: header
Path Parameters
The cloud name of your product environment.
The type of resource (image, video, or raw).
Value in
- "image"
- "video"
- "raw"
Request Body
application/json
The asset to destroy and related options.
The API key to use for the request. This is automatically computed by the Cloudinary's SDKs.
The timestamp to use for the request in unix time. This is automatically computed by the Cloudinary's SDKs.
int64(Required for signed REST API calls) Used to authenticate the request and based on the parameters you use in the request. When using the Cloudinary SDKs for signed requests, the signature is automatically generated and added to the request. If you manually generate your own signed POST request, you need to manually generate the signature parameter and add it to the request together with the api_key and timestamp parameters.
The public ID of the asset to destroy.
All supported delivery types.
Whether to invalidate CDN cached copies of the asset.
falseURL to receive a notification when the operation is complete.
uriResponse Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1_1/my_cloud/image/destroy" \ -H "Content-Type: application/json" \ -d '{ "public_id": "string" }'{ "result": "ok"}Upload a single chunk of a large file POST
Uploads a single chunk of a large file as part of a chunked upload process. This enables efficient upload of large files with the ability to resume interrupted uploads. Each request uploads one chunk of the file. It is required for any files that are larger than 100 MB. This is often relevant for video files, as they tend to have larger file sizes. Minimum chunk size is 5 MB. The `file` field accepts either the chunk bytes (multipart) or an HTTP/HTTPS URL. When a URL is supplied, Cloudinary downloads it and validates the response `Content-Length` against the chunk-size contract (exact match in the uniform-size flow; within 5 MB floor and 5 GiB cap in explicit-order mode) before storing any bytes. A mismatch aborts with 400 and persists no state. The remote server must return a `Content-Length` header; chunked transfer-encoded responses are rejected. **Explicit-order totals** (`X-Upload-Part-Number`): `X-Upload-Total-Parts` may be omitted on non-terminal chunks until the session total *N* is established by any earlier chunk that sent the header. After *N* is known, the chunk for part index *N* must include `X-Upload-Total-Parts: N`. Whenever the header appears, its value must be the same integer *N* for that `X-Unique-Upload-Id` (no conflicting totals).
Create image from text POST
Dynamically generates an image from a specified text string.