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
    • faqs
      • get faqs
    • specializations
      • get specialization areas
    • finance
      • transactions - all
      • transactions - earnings
      • transactions - purchases
      • transactions - withdrawals
      • web - balance top-up
      • withdraw coins
    • 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
    • signed-urls
      • files
    • support
      • get open ticket
      • get ticket messages
    • user
      • update user
      • change password
      • get 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
      • verification - add background info
    • users
      • get users
  • wss
    • alert
    • auth
    • call
    • chats
    • messaging
    • ping socket
    • support
    • user
  1. wss

support

check current ticket#

before sending a support message, check if the user is already engaged in an ongoing open ticket by using the get open ticket endpoint to get the current open ticket;
on success:
if a ticket ID is returned, then new messages must be sent along the ticket ID;
else, if there were no ticket returned, it means the user is starting a new ticket, then the first message can be sent without a ticket ID.
after the first message has been sent, a ticket ID should be returned, which must be used to send new messages;

send a support message#

receive a message#

listen for new support messages;

get support messages#

update messages#

the response from here is sent to all recipients in the chat with the same action type, update-support-messages;
example of such request is;
Modified at 2025-09-16 09:21:38
Previous
ping socket
Next
user
Built with