Sqabl APIs
  1. https
Sqabl APIs
  • https
    • v1
      • Auth
        • Sign Up
        • Sign In
        • Sign Out
        • Refresh Access Token
        • Get user by token
        • Change password
      • OTP
        • Verify OTP
        • Generate OTP
        • OTP Status
      • User
        • Get user
        • Get user by token
        • Update user
        • Get user's followers
        • Get user's followees
        • Get user's referred members
        • Get user's interacted items
        • Get user's bookmarks
        • Flag a user
        • Follow user
        • Unfollow user
        • Block a user
        • Unblock a user
        • Delete user's picture
        • Delete user
      • Users
        • Get users
      • Arenas
        • Get arenas
        • Create an arena
        • Invite users to arenas
      • Arena
        • Get arena
        • Update arena
        • Join an arena
        • Leave an arena
        • Get arena members
        • Add users to arena
        • Remove members from an arena
        • Update an arena member
      • Posts
        • Get posts
        • Create a post
      • Post
        • Get a post
        • Update a post
        • Delete a post
        • Flag a post
        • Flame a post
        • Unflame a post
        • Save a post
        • Unsave a post
        • Hide a post
        • Get post participants
        • Participate in a post
        • Get post comments
        • Comment on a post
      • Comment
        • Get comment
        • Delete a comment
        • Flag a comment
        • Flame a comment
        • Unflame a comment
        • Save a comment
        • Unsave a comment
      • Alerts
        • Get user's alerts
        • Mark some or all alerts read
      • Flags
        • get flags
      • Faqs
        • get faqs
      • Interests
        • get interests
      • Search
        • get popular search keywords
      • Signed Upload URL
        • get signed url for upload
    • v2
      • alerts
        • get alerts
      • arena
        • create post
        • get arena
        • get arena posts
        • get fans
        • get members
        • get moderators
        • update arena
      • arenas
        • get arenas
        • create arena
      • auth
        • get user by access token
        • get user by refresh token
        • sign in
        • sign up
      • comment
        • get comment
        • get replies
        • flame comment
        • unflame comment
        • save comment
        • unsave comment
      • existence
        • check email
        • check username
      • post
        • get post
        • flame post
        • unflame post
        • update post
        • participate in a post
        • get all participants
        • get opposing participants
        • get supporting participants
        • get option participants
        • save post
        • unsave post
        • get comments
        • comment on a post
        • get opposing comments
        • get supporting comments
      • posts
        • get posts
        • get trending posts
        • get your-feed posts
      • signed-urls
        • files
      • support
        • send a message
        • get messages
      • user
        • get user
        • get user's posts
        • get arenas user belongs
        • get arenas user owns
        • update user
        • follow user
        • unfollow user
        • block user
        • unblock user
        • get user's interactions
        • get user's bookmarks
        • get user's followees
        • get user's followers
        • get user's arenas
        • get user's referrals
      • users
        • get users
  1. https

V2 General Release Notes

Query Params#

the checkUserActivities or such, is no longer suppoted in the query params; the viewer's access token in the header would suffice

Uploaded File#

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-07-04 17:54:44
Previous
get signed url for upload
Next
alerts
Built with