Skip to main content
Fetch Connections
Returns a paginated list of accepted connections for the authenticated user. Each entry includes the connected user’s public profile. Unlike the user-scoped endpoint, this route always returns data for the current authenticated user.
Users with a block between them and the acting user (the signed-in user, or the user a service key names in actingUserId), in either direction, are excluded from the results. Requires the moderation bundle.

Query Parameters

number
Page number for pagination. Defaults to 1.
number
Number of results per page. Defaults to 20. Max 100.
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.
string
Service key only, and required with one: the user this request acts as. Their accepted connections are listed. A user token always acts as its own user and must not send it (400 connection/acting-user-not-allowed).

Response

On success, returns HTTP 200 with a paginated response:
array
Array of connection entries.
object
Pagination metadata.

Error Responses

A service key sent no actingUserId.
A user token sent actingUserId, even naming its own user. Only a service key names the user it acts as; a user token always acts as its own user.
Returned when a service key names an actingUserId that isn’t a user in this project.
The request sent userId. On this route the user a service key acts as is actingUserId.With a service key:
With a user token, or with no credentials:

See Also