Talkamie APIs
  1. wss
Talkamie APIs
  • https
    • alert
    • alerts
      • get alerts
    • auth
      • get user by token
      • sign up
      • sign in
      • sign out
    • availability
      • get custom availability
      • get weekly availability
      • set custom availability
      • set weekly availability
    • call
      • get call
    • calls
      • get call histories
    • chat
      • get chat
      • get messages
    • chats
      • get frequent chats
      • get unread chats
      • get chats
    • connect-request
    • connect-requests
      • get pending connection requests
      • get users you're in connection with
    • interests
      • get interests
    • otp
      • generate otp
      • verify otp
    • reviews
      • get your reviews
    • schedule
      • get a schedule
      • update a schedule
      • delete schedule
    • schedules
      • get all schedules
      • get past schedules
      • get upcoming schedules
    • user
      • update user
      • change password
      • get user
      • background check on user
      • delete user
      • schedule a call
      • clear schedules
      • send connection request
      • cancel connection request
      • accept connection from user
      • reject connection request
      • send message request
      • cancel message request
      • accept message request
      • reject message request
      • get user reviews
      • review a user
      • update review
      • delete review
    • users
      • get users
  • wss
    • alert
    • auth
    • call
    • call-signal
    • chats
    • messaging
    • ping socket
  1. wss

messaging

message request#

if both users do not have mutual "connection", i.e., there hasn't been an acceptance to a connection request between them, then, there is a need to send a message request, before a conversation can continue in a chat.
use the /user/{id}/message/request to send a message request;
once the request has been posted, the receiver gets a socket event alert with the following props;

send a message#

this is possible only if there's a mutual connection already, or if the message request has been accepted.

receive a message#

after a message has been sent, the connected receiver gets the message, while the socket sends an event action, new-message;
⚠️sometimes, messages can also be received from alerts emitted from the socket, for instance, when a new schedule has been made, its message is sent along the alert props;

get messages#

update messages#

the response from here is sent to all recipients in the chat with the same action type, update-messages;
example of such request is;
Modified at 2025-06-15 18:02:27
Previous
chats
Next
ping socket
Built with