Ok, I see the different API endpoints now:
To update raw file metadata (default metadata values that are stored in the data_meta d/b table like imageheight, name etc), then use the POST /a/meta/set/{NodePath} endpoint, with Body payload like:
{
“Metadatas”: [
{
“Namespace”: “<namespace_name>”,
“JsonMeta”: “{“<namespace_name>”:“new value”}”
}
]
}
To update custom (user metadata namespaces), then use PUT https://localhost:8123/a/user-meta/update endpoint with a Body payload like:
{
“MetaDatas”: [
{
“JsonValue”: “{\“usermeta-photographer\”:\“new foto name\”}”,
“Namespace”: “usermeta-photographer”,
“NodeUuid”: “f6450ab6-0951-4c81-a7b6-46fd63c0a123”
}
],
“Operation”: “PUT”
}
(“Operation” is allowed to be PUT or DELETE)
Slightly different as you’ll need to first get/know the UUID of the file you’re updating the metadata for. But this way I’ve tested working with a file that has the metadata updated from the frontend webapp and/or programmatically via the API web request.