Skip to content

From 7.4 roomID is now required even if channel is passed in chat.postMessage. #35923

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jadolg opened this issue May 3, 2025 · 0 comments

Comments

@jadolg
Copy link

jadolg commented May 3, 2025

Description:

While testing the integration with v7.4.0, looks like roomID is now required even if channel is passed in chat.postMessage.

This change, if intentional, is not documented.

See here the discussion.

Steps to reproduce:

note: I'm going to use the Python wrapper since it's easier to explain that way in examples but the procedure is the same with curl.

  1. Post a message via API.
logged_rocket.chat_post_message(
        "text1",
        channel="GENERAL",
    ).json()
  1. Now try Responding to that message
logged_rocket.chat_post_message(
        "text2",
        channel="GENERAL",
        tmid=msg1_id,
    ).json()

Actual behavior:

The API will respond this to the second call:

{'error': "must have required property 'roomId'\n must NOT have additional properties\n must match exactly one schema in oneOf [invalid-params]", 'errorType': 'invalid-params', 'success': False}

Server Setup Information:

  • Version of Rocket.Chat Server: 7.4 to 7.5
  • License Type:
  • Number of Users:
  • Operating System:
  • Deployment Method: Docker
  • Number of Running Instances:
  • DB Replicaset Oplog:
  • NodeJS Version:
  • MongoDB Version:

Client Setup Information

  • Desktop App or Browser Version:
  • Operating System:

Additional context

Relevant logs:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant