Add or remove file tags | Uploadcare docs

Adds and/or removes tags in a single atomic operation. add and delete are both optional and default to [].

Delete is applied first, then add — a tag can be removed and re-added in the same request. Tags in add that are already present are silently skipped. Tags in delete that are not present are silently ignored.

If the resulting tag count would exceed 50, the request fails with 400. An empty body {} is valid and returns the current tag state unchanged.

Tags are normalized before storage (lowercased, whitespace-stripped, duplicates removed).

Adds and/or removes tags in a single atomic operation. `add` and `delete` are both optional and default to `[]`. Delete is applied first, then add — a tag can be removed and re-added in the same request. Tags in `add` that are already present are silently skipped. Tags in `delete` that are not present are silently ignored. If the resulting tag count would exceed 50, the request fails with 400. An empty body `{}` is valid and returns the current tag state unchanged. Tags are normalized before storage (lowercased, whitespace-stripped, duplicates removed).

Authentication

Authorizationstring

Every request made to https://api.uploadcare.com/ MUST be signed. HTTPS SHOULD be used with any authorization scheme.

Requests MUST contain the Authorization header defining auth-scheme and auth-param: Authorization: auth-scheme auth-param.

Every request MUST contain the Accept header identifying the REST API version: Accept: application/vnd.uploadcare-v0.7+json.

There are two available authorization schemes:

For production: Uploadcare, a scheme where a signature, not your Secret API Key MUST be specified. Signatures SHOULD be generated on backend.
For quick tests: Uploadcare.Simple, a simple scheme where your Secret API Key MUST be specified in every request’s auth-param.

Every request made to `https://api.uploadcare.com/` MUST be signed. HTTPS SHOULD be used with any authorization scheme. Requests MUST contain the `Authorization` header defining `auth-scheme` and `auth-param`: `Authorization: auth-scheme auth-param`. Every request MUST contain the `Accept` header identifying the REST API version: `Accept: application/vnd.uploadcare-v0.7+json`. There are two available authorization schemes: * For production: `Uploadcare`, a scheme where a `signature`, not your Secret API Key MUST be specified. Signatures SHOULD be generated on backend. * For quick tests: `Uploadcare.Simple`, a simple scheme where your [Secret API Key](https://app.uploadcare.com/projects/-/api-keys/) MUST be specified in every request's `auth-param`.

Path parameters

uuidstringRequiredformat: "uuid"

File UUID.

Request

This endpoint expects an object.

addlist of stringsOptional

Tags to add. Tags already present are silently skipped.

deletelist of stringsOptional

Tags to remove. Tags not present are silently ignored.

Response

Tags updated successfully.

tagslist of strings

Resulting tag list in storage order.

addedlist of strings

Tags that were actually added (not already present).

deletedlist of strings

Tags that were actually removed.

Errors

400

Bad Request Error

401

Unauthorized Error

404

Not Found Error

406

Not Acceptable Error

415

Unsupported Media Type Error