Open Cloud Messaging API V2 [Beta]

Updates Announcements
#1

Hello Creators,

We are pleased to announce the beta launch of the Open Cloud Messaging API V2. This API enables the publication of messages to game servers of your experiences from external sources outside the Roblox environment. This allows integration with your own system for live announcements, running LiveOps events, banning bad actors in real time, and other functions leveraging the MessagingService.

Message publication can now be done through the new endpoint on Open Cloud, following the same procedures as other familiar APIs on the Open Cloud platform.

curl \
--location \
--request POST \
'https://apis.roblox.com/cloud/v2/universes/{universe}:publishMessage' \
-H 'x-api-key: abc...' \
-H 'Content-Type: application/json' \
--data '{"topic":"the topic", "message":"message to publish"}'

Please note the change in the Open Cloud resource URL and the relocation of the topic from the URL to the request body. Refer to the Open Cloud API documentation for Messaging at Universe | Documentation - Roblox Creator Hub.

As always, please do not hesitate to contact us if you have any questions or encounter any issues.

Sincerely,
The Roblox Creator Services Team

145 Likes
Weekly Recap: January 13-17, 2025
#2

This topic was automatically opened after 10 minutes.

#3

Any notable improvements over v1? And assuming I’m reading the documentation correctly, I take it that v2 functions identically to v1 with the only difference being the topic inside request body instead of the path parameters?

25 Likes
#4

Are there any plans to add an API for reserving servers from the cloud? It would be very useful for making custom matchmaking systems.

13 Likes
#5

There are no user-facing improvements other than onboarding to the Open Cloud v2 to benefit from the security built into the platform and provide the same user experience as other services on the platform.

16 Likes
#6

Are there any technical reasons for only allowing strings to be published through the CloudAPI or are other datatypes just not planned/implemented currently?

12 Likes
#8

good now make TCPService to go along with HTTPService

16 Likes
#9

I just realized you can use the Luau Execution API to do this lol, cool workaround for now
@DevelopmentDeadline

image
image871×315 42.6 KB

18 Likes
#10

With is, is there any significant reason for an Open Cloud developer to migrate from the v1 to v2 API?

11 Likes
#11

I would assume security and that V1 would be retired early, so mostly future proofing.

7 Likes
#12

waiting for the day we can connect to a websocket server and subscribe to MessageService topics…

9 Likes
#13

This is very helpful as making our own systems might take a bit and might cost money.

8 Likes
#14

Waiting for the day we can make a TCP server and have clients connect to it…

7 Likes
#15

waiting for the day we can connect to websockets or TCP/UDP servers natively

9 Likes
#16

Is this how we can message throurh servers??

8 Likes
#17

Exactly!!! That’s what’s roblox needs to add!

6 Likes
#19

I’m also curious about this. So many cool features released yet particularly I think this is one of the most waited. This would be efficient for some systems, mainly matchmaking.

6 Likes
#21

I don’t know if you’re interested in something like this but I wrote something like a WebSocket for Roblox: GitHub - metrik-tech/pulse. Not 100% done yet, needs a Lua client but that should be fairly straightforward to implement.

It’s built using Cloudflare Workers/Durable Objects, and should be plenty efficient & cheap to run if all you want is realtime comms between a server and Roblox.

6 Likes
#22

Is it possible to make it so that only a specific place/game instance receives a message? This would make it at least slightly more secure to implement something like websockets in Roblox.

#23

You need to pass that as arguments within your publish.