users module reads and updates user profiles and lets the logged-in user act on the social graph of an arbitrary target user, addressed by userId.
In the follow and connection helpers below, userId is always the target — the user being followed, the other party in a connection, or the user whose followers you’re reading. The actor is always the logged-in token holder. To act on your own graph (your own followers, the users you follow, your own connections and pending requests), use the follows and connections modules instead.
fetchUserById
Fetches a user by their internal Sublay user ID.string
required
The Sublay user ID.
string
Comma-separated list of associations to populate.
Promise<User>
fetchUserByForeignId
Fetches a user by your application’s own user identifier.string
required
Your application’s user identifier.
string
Comma-separated list of associations to populate.
Promise<User>
fetchUserByUsername
Fetches a user by their username.string
required
The user’s unique username.
string
Comma-separated list of associations to populate.
Promise<User>
fetchUserSuggestions
Returns users whose name or username matches a partial query string. Useful for mention autocomplete.string
required
Partial name or username to search for.
Promise<User[]>
checkUsernameAvailability
Checks whether a username is available.string
required
The username to check.
Promise<{ available: boolean }>
updateUser
Updates a user’s profile, optionally uploading a new avatar and/or banner image. A user token may only update its own profile.string
required
The Sublay user ID to update. A user token may only update itself.
string
New display name.
string
New username. Must be available.
string
New avatar URL.
string
New bio text.
string
ISO 8601 date string for the user’s birthdate.
object
Geographic location
{ latitude: number; longitude: number }, or null to clear it.object
Updated public metadata (
Record<string, any>).object
Updated secure metadata (
Record<string, any>, not exposed in public responses).object
A new avatar image to upload:
{ file: Blob | File; options: ImageOptions }.object
A new banner image to upload:
{ file: Blob | File; options: ImageOptions }.When
avatarFile or bannerFile is supplied the request is sent as
multipart/form-data carrying the browser File/Blob. The image options
(an ImageOptions object whose mode selects a processing strategy) are sent
alongside the file.Promise<AuthUser>
fetchFollowersByUserId
Returns a paginated list of users following the target user.string
required
The Sublay user ID whose followers to fetch.
number
Page number (1-indexed). Defaults to
1.number
Results per page. Defaults to
20.string
Optional search term. Filters the list to users whose username or name contains this text (case-insensitive). When omitted, no filtering is applied.
string
Restricts which field
query matches against — username or name. When omitted, query matches either field.Promise<PaginatedResponse<FollowListItem>>
fetchFollowersCountByUserId
Returns the total number of followers for the target user.string
required
The Sublay user ID.
Promise<{ count: number }>
fetchFollowingByUserId
Returns a paginated list of users that the target user is following.string
required
The Sublay user ID whose following list to fetch.
number
Page number (1-indexed). Defaults to
1.number
Results per page. Defaults to
20.string
Optional search term. Filters the list to users whose username or name contains this text (case-insensitive). When omitted, no filtering is applied.
string
Restricts which field
query matches against — username or name. When omitted, query matches either field.Promise<PaginatedResponse<FollowListItem>>
fetchFollowingCountByUserId
Returns the number of users the target user is following.string
required
The Sublay user ID.
Promise<{ count: number }>
fetchConnectionsByUserId
Returns a paginated list of the target user’s established connections.string
required
The Sublay user ID whose connections to fetch.
number
Page number (1-indexed). Defaults to
1.number
Results per page. Defaults to
20.string
Optional search term. Filters the list to connections whose connected user’s username or name contains this text (case-insensitive). When omitted, no filtering is applied.
string
Restricts which field
query matches against — username or name. When omitted, query matches either field.Promise<PaginatedResponse<EstablishedConnection>>
fetchConnectionsCountByUserId
Returns the number of established connections for the target user.string
required
The Sublay user ID.
Promise<{ count: number }>
createFollow
The logged-in user follows the target user.string
required
The user being followed (the target).
Promise<Follow>
deleteFollow
The logged-in user unfollows the target user.string
required
The user being unfollowed (the target).
This unfollows by the target’s
userId. To delete one of your own follow
relationships by its record ID, use
follows.deleteFollow, which takes a followId.Promise<void>
fetchFollowStatus
Returns whether the logged-in user follows the target user.string
required
The user whose follow relationship is being checked (the target).
Promise<{ isFollowing: boolean; followId?: string; followedAt?: string }>
requestConnection
Sends a connection request from the logged-in user to the target user.string
required
The user the connection is requested with (the target).
string
Optional message to include with the request.
Promise<ConnectionRequestResponse> — the created/pending connection.
fetchConnectionStatus
Returns the connection status between the logged-in user and the target user.string
required
The other user in the connection (the target).
Promise<ConnectionStatusResponse>
removeConnectionByUserId
Removes the connection with the target user — withdrawing a sent request, declining a received one, or disconnecting an established connection, depending on the current state.string
required
The other user in the connection (the target).
Promise<RemoveConnectionByUserIdResponse>
Blocking
User-to-user blocking is part of the trust & safety moderation bundle. These functions require that bundle; a project without it returns403 database/tables-not-available. The blocker is the token holder — there is no actingUserId.
Blocking severs interaction between two users across every Sublay surface and is non-disclosing — the blocked user is never notified. See Moderation — Blocking for the full enforcement behavior.
createBlock
Blocks a user. On a new block, existing follows and connections between the pair are torn down (both directions). Idempotent — re-blocking succeeds. Self-block is rejected server-side.string
required
The user being blocked (the target). The blocker is the token holder.
Promise<BlockResponse> — { id, blockerId, blockedId, createdAt }.
deleteBlock
Unblocks a user. Idempotent; restores nothing.string
required
The user being unblocked (the target).
Promise<void>
fetchBlockStatus
Checks whether the token holder blocks the target user. Outbound-only — it never reveals whether the target has blocked the token holder.string
required
The user whose block relationship is being checked (the target).
Promise<BlockStatusResponse> — { blocked: boolean; blockId?: string; createdAt?: string }.
fetchBlockedUsers
Returns a paginated list of the users the token holder has blocked (their outbound blocks), each row carrying a public profile summary. This block list is private to the blocker.number
Page number (1-indexed). Defaults to
1.number
Results per page. Defaults to
20. Max 100.Promise<PaginatedResponse<BlockedUserListItem>>, where each BlockedUserListItem is { id, blockedUser, createdAt }.
