Realtime send() is automatically falling back to REST API

[DominikLevitsky]

I am using @supabase/ssr on my server and sending realtime messages, like described in the docs:

const channel = supabase.channel(`presence:${user.id}`, { config: { private: true } });
await channel.send({ type: 'broadcast', event: 'client-join', payload: {...} });

The messages are sent, but I am getting overwhelmed with logs:

Realtime send() is automatically falling back to REST API. This behavior will be deprecated in the future. Please use httpSend() explicitly for REST delivery.

Can the logs be disabled somehow or am I doing something wrong?

"@supabase/ssr": "^0.8.0"
Node 22.22.0

[Byt3Sh0ck]

Got the same issue using supabasejs. httpSend doesnt seem to be mentioned anywhere in their docs either.

[swanson8r]

Context

The feature was introduced into supabase-js, which is a dependency of ssr.

• Here's the feature PR: feat(realtime): realtime explicit REST call supabase-js#1751
• Changelog shows the first full release with this change as v2.76.0

Suggested Mitigation Steps

1. Check to confirm when your version of @supabase/supabase-js was updated to ^2.76 : This will provide further context for why the warning logs are appearing.
2. Follow the warning message and replace await channel.send( with await channel.httpSend(

[Byt3Sh0ck]

Fixed it. the issue was that the signature of httpsend is different to normal send.

Instead of doing: "channel.send({ type: 'broadcast', event: 'my-event', payload:..."
Its: "channel.httpSend('my-event', { ... })"

Maybe that fixes it for you too OP.