User Followings
Fetch followings for a given user. Each request returns a chunk of 100 followings. See the `cursor` and `page_token` query parameters below for information on how to manage pagination (fetch more followings). Note: if the `secUid` doesn't exists, the cost is just 1 unit.
API Pricing (per request): 2 units
API usage examples
- secUid does not exist:
-> null returned.
Cost: 1 unit - secUid exists and has 40 followings:
-> 40 followings returned.
Cost: 2 units - secUid exists and has more than 100 followings:
-> 100 followings and cursor for next request returned.
Cost: 2 units
Try the API
Request
- Base URL: https://ensembledata.com/apis
- URL: https://ensembledata.com/apis/tt/user/followings
- Auth: none declared
Query parameters
The id of the user.
The secondary id of the user.
Parameter to manually handle pagination. Each response contains a nextCursor which can be used to retrieve the next page of results by sending it as the next cursor. If the nextCursor is not present in the response, it means that there are no more results to retrieve.
Secondary cursor to manage pagination (initially empty). The page_token for next request is returned by the previous response as the nextPageToken. This works in the same way as the cursor parameter.
Private token assigned to each client to access the APIs.
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.