Update server metadata
Deprecated
PUT
/servers
/servers with the documented body, query parameters, headers, or multipart fields. Prefer the newer authenticated /v1/... integration API where available.{ status, message, data } wrapper.400 invalid request body, query, ObjectId, pagination, file format, or missing required field.401 missing, invalid, expired, or insufficient API key/token.403 key is valid but cannot access this community/channel/user/resource, where supported by the service.404 route or target resource was not found. Several legacy root routes returned 404 on https://api.returning.ai during smoke testing and need backend confirmation before external use.409 duplicate or conflicting state for create/update operations, where applicable.500 unexpected Returning.AI service error.Compatibility endpoint retained for older integrations. Do not use this endpoint for new integrations unless Returning.AI specifically tells you to maintain a legacy flow. Prefer the current
/v1/... endpoint in the matching non-Legacy category when one exists.Request
Header Params
Body Params application/json
Responses
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request PUT 'https://api.returning.ai/servers' \
--header 'x-api-key: **************' \
--header 'Content-Type: application/json' \
--data '{
"name": "TR5-new1-Sep-Edited",
"url_meta": {
"title": "Genesiv SEO Title",
"description": "Genesiv SEO Description",
"imageLogo": "https://chartsnapshot-genesiv.s3.amazonaws.com/895e8f10-f5eb-11ef-ae51-7be624d0dfda_image.webp"
}
}'Response Response Example
200 - Success Example
{
"meta": {
"success": true,
"message": "Server has been updated successfully",
"devMessage": "Server has been updated successfully"
},
"body": {}
}Modified at 2026-05-18 17:03:37