Edit media metadata

PATCH

/media/{id}

curl --request PATCH \
  --url https://api.dropslate.top/v1/media/example \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "title": "example", "description": "example", "tags": [ "example" ], "folderId": "example", "pinned": true }'

• Production

Requires write.

Authorizations

• bearerAuth

Parameters

Path Parameters

id

required

string

Request Body

Media typeapplication/json

object

title

string

nullable

description

string

nullable

tags

Array<string>

folderId

string

nullable

pinned

boolean

Example^generated

{
  "title": "example",
  "description": "example",
  "tags": [
    "example"
  ],
  "folderId": "example",
  "pinned": true
}

Responses

200

The media row as edited.

Media typeapplication/json

object

id

string

kind

string

Allowed values: image video

originalName

string

mime

string

size

integer

status

string

Allowed values: uploading processing ready failed

failReason

string

nullable

width

integer

nullable

height

integer

nullable

durationMs

integer

nullable

folderId

string

nullable

tags

Array<string>

pinned

A pinned file is never removed after publishing.

boolean

publishedAt

string format: date-time

nullable

purgedAt

When the bytes were removed, 72 hours after a post with the file went live (1.3.0). The row, name and metadata stay; a post naming it is refused with media_purged.

string format: date-time

nullable

thumbnailUrl

string

nullable

createdAt

string format: date-time

Example

{
  "kind": "image",
  "status": "uploading"
}

403

The key is missing the “write” scope, or this route needs a signed-in session instead of a key.

Media typeapplication/json

object

code

required

string

message

required

string

hint

string

Example

{
  "code": "not_found",
  "message": "The post does not exist.",
  "hint": "Check the id and try again."
}

404

Does not exist, or belongs to a different workspace - the two look identical from here.

Media typeapplication/json

object

code

required

string

message

required

string

hint

string

Example

{
  "code": "not_found",
  "message": "The post does not exist.",
  "hint": "Check the id and try again."
}