remote_archive_config row.service-password, access-token and refresh-token entirely, so the usual read-modify-write round trip carries none of them and the stored values survive untouched. Sending one replaces it; sending it empty is also treated as "leave it alone" rather than "clear it", so a form that renders a blank password field cannot wipe a working credential.Authorization: Bearer ********************curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//recording-storage/' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"service-name": "string",
"service-vendor": "string",
"service-url": "string",
"service-path": "string",
"service-login": "string",
"service-password": "string",
"admin-email": "string",
"access-token": "string",
"refresh-token": "string",
"enabled": "yes",
"status": "string",
"parameter": "string"
}'{
"code": 0,
"message": "string"
}