Request Parameters
Name | Type | Description | Location | Required | Default | Options |
---|---|---|---|---|---|---|
ThreadId | int | Thread Id | Query String | Required | ||
ParentReplyId | int | Parent Reply Id | Query String | Optional | ||
StartReplyId | int | Start Reply Id | Query String | Optional | ||
EndReplyId | int | End Reply Id | Query String | Optional | ||
CreatedStartDate | DateTime | Created start date. Only filters first level of replies returned. | Query String | Optional | ||
CreatedEndDate | DateTime | Created end date. Only filters first level of replies returned. | Query String | Optional | ||
ThreadedSortBy | string | Sort threaded replies by. Sort options include CreatedDate or Votes | Query String | Optional | ||
ThreadedSortOrder | string | Sort order threaded replies. 'Ascending' or 'Descending' | Query String | Optional | ||
FlattenedSortBy | string | Sort of flattened replies. Sort options include CreatedDate or Votes | Query String | Optional | ||
FlattenedSortOrder | string | Sort order of flattened replies. 'Ascending' or 'Descending' | Query String | Optional | ||
RootPageSize | int | Number of first level replies to return. Max of 100. | Query String | Optional | 20 | |
FlattenedDepth | int | Specify the depth at which all child replies will be wrapped under the last level of threaded replies. Zero-based index. Max of 9. | Query String | Optional | 2 | |
ChildPageSize | int | Specifies the number of child records to return per first level replies. Max of 50. | Query String | Optional | 10 | |
PostTarget | string | Render target. Options: Unknown, Web, Syndication, Offline, Other, Print, Nntp, Email, WebQuote, WebServices. | Query String | Optional | ||
ThreadId | int | Thread Id | Query String | Required | ||
ReplyId | int | Reply Id | Query String | Required | ||
ThreadedSortBy | string | Sort threaded replies by. Sort options include CreatedDate or Votes | Query String | Optional | ||
ThreadedSortOrder | string | Sort order threaded replies. 'Ascending' or 'Descending' | Query String | Optional | ||
FlattenedSortBy | string | Sort of flattened replies. Sort options include CreatedDate or Votes | Query String | Optional | ||
FlattenedSortOrder | string | Sort order of flattened replies. 'Ascending' or 'Descending' | Query String | Optional | ||
FlattenedDepth | int | Specify the depth at which all child replies will be wrapped under the last level of threaded replies. Zero-based index. Max of 9. | Query String | Optional | 2 | |
PageSize | int | Number of replies to return. Max of 100. | Query String | Optional | 20 | |
Direction | string | Specifies the direction paging occurs, either up from the ReplyId passed in to the root reply, or down from the root reply for the ReplyId passed in. 'FromRootReply', 'FromReply' | Query String | Optional | FromReply | |
PostTarget | string | Render target. Options: Unknown, Web, Syndication, Offline, Other, Print, Nntp, Email, WebQuote, WebServices. | Query String | Optional |
Example Requests
C# REST SDK
This example uses the REST SDK to access the Community REST API within a .Net C# application. In the example, USER_NAME
is the user name of the effective user for the request and OAUTH_CLIENT_ID
and OAUTH_SECRET
are the OAuth client ID and secret, respectively, associated to this application as configured in Administration > Integration > OAuth Clients with the "Client Credentials" grant type enabled. See the documentation for the REST SDK for more details about installation, configuration, and usage options.
var host = new ClientCredentialsRestHost("USER_NAME", "https://mysite.com/", "OAUTH_CLIENT_ID", "OAUTH_SECRET"); var response = host.GetToDynamic(2, "forums/threads/{threadid}/replies/threaded.json", false, new RestGetOptions { PathParameters = new System.Collections.Specialized.NameValueCollection { { "threadid", "6" } }, QueryStringParameters = new System.Collections.Specialized.NameValueCollection { { "ReplyId", "6" } } });
Widget Javascript
This example uses the rest JavaScript API to access the Community REST API within the Community web UI. When accessing the REST API through the javascript API, the effective user is the current contextual user of the web interface.
jQuery.telligent.evolution.get({ url: jQuery.telligent.evolution.site.getBaseUrl() + 'api.ashx/v2/forums/threads/{threadid}/replies/threaded.json', data: { 'threadid': '6', 'ReplyId': '6' }, success: function(response) { } });
cURL
This example uses the cURL command-line HTTP utility. ENCODED_TOKEN
in the example is the base64-encoded concatenation of the user's API key (created from the user's profile), a colon (:), and the user's user name. Learn more about using the REST API.
curl -H "Rest-User-Token: ENCODED_TOKEN" -X GET https://mysite.com/api.ashx/v2/forums/threads/6/replies/threaded.xml?ReplyId=6