GET /api/v2/users/{user_id}/tickets/followed

Lists tickets the specified user is following.

Servers

https://{subdomain}.{domain}.com

Path parameters

Name	Type	Required	Description
`user_id`	Integer	Yes	The id of the user

Query parameters

Name	Type	Required	Description
`page`		No	Pagination parameter. Supports both traditional offset and cursor-based pagination: Traditional: `?page=2` (integer page number) Cursor: `?page[size]=50&page[after]=cursor` (deepObject with size, after, before) These are mutually exclusive - use one format or the other, not both.
`sort_order`	String	No	Sort order. Defaults to "asc" Valid values: `"desc"` `"asc"`
`per_page`	Integer	No	Number of records to return per page. Note: Default and maximum values vary by endpoint. Check endpoint-specific documentation for limits.
`exclude_archived`	Boolean	No	If true, excludes archived tickets from the results.
`sort_by`	String	No	Sort by Valid values: `"deleted_at"` `"id"` `"subject"`

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.