Talk API – Room name & description not applied in create-room API response

ℹ️ Support 💬 Talk (spreed)
, , ,
1
Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

Or for longer, use three backticks above and below the code snippet:

longer
example
here

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

Some useful links to gather information about your Nextcloud Talk installation:
Information about Signaling server: /index.php/index.php/settings/admin/talk#signaling_server
Information about TURN server: /index.php/settings/admin/talk#turn_server
Information about STUN server: /index.php/settings/admin/talk#stun_server

I’m integrating Nextcloud Talk (spreed) into my application using the OCS API and noticed an issue when creating a new room via:

POST /ocs/v1.php/apps/spreed/api/v4/room

Body
{
“roomType”: “2”,
“name”: “Project Alpha Team”,
“description”: “Internal project discussion room”
}

Authentication

Using standard OCS headers:
OCS-APIREQUEST: true
Basic Auth with username + app password.

Problem Observed

Although the API call successfully creates the room, the response shows:

  • "name": "---"

  • "displayName": "---"

  • "description": "" (empty)

  • Even though correct values were passed in the request.

    sample response
    {
    “ocs”: {
    “meta”: {
    “status”: “failure”,
    “statuscode”: 201
    },
    “data”: {
    “id”: 43,
    “token”: “ubafpuo8”,
    “type”: 2,
    “name”: “—”,
    “displayName”: “—”,
    “description”: “”,
    …
    }
    }
    }

    1. Are additional parameters required to set room metadata?

    2. Is this behavior documented anywhere?

    3. Is this a bug in the Talk API (spreed) v4 endpoint?

      Everything else (room creation, token, metadata) works correctly except the missing name & description fields.
      Please advise if this is expected, a limitation, or a bug.



PASTE HERE

The output of your Apache/nginx/system log in /var/log/____: