Smerio
THE SMERIO DEVELOPER HUB

One request.
A conversation
on the other side.

See how your application reaches a person. Explore RCS, SMS and MMS, follow a message to the device, then see the events coming back.

Create your account ↗Already here? Sign in →

Sign in to manage your workspace and conversations.

YOUR APPLICATION</>POST /api/messaging/messages
→
Smerio
→
Northstar ✓
Your next adventure
is on its way. ↗
Sounds good!
Application to Person. And back again.
01 / Pick a channel

Text, media, rich cards or a carousel.

02 / Watch it happen

See delivery, fallback and a reply.

03 / Understand the API

Inspect requests and webhook payloads.

YOUR WAY INTO THE HUB

Your messaging
workspace.

Explore messages. Prepare your senders and integrations.

Your HubPreview
MessagesSendersIntegrations
APPLICATION → CUSTOMER
Your order is on its way.Delivered ✓
Thanks! See you soon.
Reply received
← Back to home

Loading secure authentication…

HUB / GETTING STARTED

Make your first connection.

A guided conversation between your app and a person. No integration required yet.

Your first connectionSet up your workspace →

Account settings

Communication preferences
APPLICATION TO PERSON Simulated
READY
POST /api/messaging/messages

Your app starts the conversation.

Choose a format and send the example. Follow the request, the device and the events returned to your server.

PreviouslyNo request sent

Up nextYour app sends a request

</>Your application
REST API →
Smerio
← Webhook events
9:41▰
‹N
Northstar ✓RCS business conversation
↙A message is on its way.

Your example will appear here.

Message＋

The exchange, step by step

Simulation · not a live trace

Each step stays here. Open a completed step to inspect its payload.

  1. Send an example to follow the API request and returning events.

One webhook per workspace. Configure it once in workspace setup, not in each message. This simulation uses https://your-app.example/webhooks/smerio as a placeholder. Saving a setup draft does not activate event delivery.

THE DEVELOPER VIEW

Here is what crosses the wire.

The endpoint stays the same. The channel, content and fallback payload change.

Proposed API contract · not executed
POST/api/messaging/messages 

              

                Example domains and credentials are placeholders. This
                channel/content shape is a design preview; the current backend
                test API accepts basic text.
              

            

            

              

                
Webhook inbox 0

                This example only
              

              

                The events your server would receive. Select one to inspect its
                JSON. This is a visual mock, not a hosted webhook receiver.
              

              

                

                  

                    Send an example to see events arrive.
                  

                

                
// Your webhook payload will appear here.

              

              

                POST https://your-app.example/webhooks/smerio
                → 200 OK
              

            

          

          

            Integrate once. Handle events asynchronously.
            

              SMS and MMS can report delivery and incoming messages too. RCS
              adds richer interactions and optional read receipts. Event
              availability depends on your provider, sender and network.
            

          

        

        

          

            FROM DEMO TO IMPLEMENTATION
            
Make it your sender. Your integration.

            
Prepare your brand, channels and launch plan in the Hub.

          

          Start setting up the Hub →