Talkamie APIs
    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

    https

    General Response#

    All responses have common properties at the first level of the returned object;
    Note that the data value depends on the enpoint invoked.

    Pagination#

    Most of the get endpoints accpets some query params to paginate your request.
    Say you're fetching users;
    initially, your request URI looks this way;
    https://baseApi/users?pageSize=4
    then, its response could contain the pagination attribute (as typed above);
    // https://baseApi/users?pageSize=4
    
    {
        "success": true,
        "statusCode": 200,
        "data": [
            "...",
            {
            "id": "some-last-user-id",
            "email": "hiseous@gmail.com",
            "displayName": "Hiseous",
            "verified": true
            }
        ],
        "pagination": {
            "lastEvaluatedKey": {
                "id": "some-last-user-id",
                "dateCreated": "2024-10-24 07:46:30.725Z"
            }
        }
    }
    on the next call, you grab the lastEvaluatedKey value;
    stringify it, then pass as a param on the next call, this way, your next request URI looks like this;
    https://baseApi/users/?pageSize=4&lastEvaluatedKey={"id":"some-last-user-id","dateFollowed":"2024-10-24 07:46:30.725Z"}
    then, if the next response contains the pagination attribute, you repeat the same process with the new pagination props from the newer response;
    // https://baseApi/users/?pageSize=4&lastEvaluatedKey={"id":"some-last-user-id","dateFollowed":"2024-10-24 07:46:30.725Z"}
    
    {
        "success": true,
        "statusCode": 200,
        "data": [
            "...",
            {
            "id": "some-another-last-user-id",
            "email": "hissy-baby@gmail.com",
            "displayName": "Hiseous",
            "verified": true
            }
        ],
        "pagination": {
            "lastEvaluatedKey": {
                "id": "some-another-last-user-id",
                "dateCreated": "2025-10-24 07:46:30.725Z"
            }
        }
    }
    You should not modify the lastEvaluatedKey, by the way.
    If the response doesn't contain pagination, then it implies the last items were fetched.

    Sending Tokens#

    When it's necessary to send an access or refresh token, use the headers. Although, cookies are sent from the server automatically if the client allows cookies.
    Headers Example#
    Modified at 2025-05-24 08:46:13
    Next
    alert
    Built with