Cisco WebEx Social API Reference Guide, Release 3.4
Post Resource Operations
Downloads: This chapterpdf (PDF - 525.0KB) The complete bookPDF (PDF - 15.05MB) | Feedback

Post Resource Operations

Table Of Contents

Post Resource Operations

Get Information about a Post

Get Information about Posts

Create a Post

Update Information about a Post

Get Information about Attachments for a Post

Add Attachments to a Post

Delete Attachments from a Post

Get Information about a Comment for a Post

Get Information about Comments for a Post

Create a Comment for a Post

Update a Comment for a Post

Delete a Comment from a Post

Add a Tag to a Post

Delete a Tag from a Post

Get Information about a Video that is Embedded in a Post or Attached to a Micropost

Attach an Video to a Micropost

Update an Attached Video in a Micropost

Delete an Attached Video from a Micropost

Get Permissions for a Post

Update Permissions for a Post

Get Users that have Marked a Designated Post as a Favorite

Get Information about Users that Like a Designated Post

Get the Number of Users that Like a Designated Post

Get Information about the Versions of a Post

Get the Differences Between Two Versions of a Post

Restore an Older Version of a Post

Get Information about All Activities that Relate to a Post


Post Resource Operations


A Cisco WebEx Social post lets Cisco WebEx Social users share text, videos, images, links, and files with people, groups, and communities. The Cisco WebEx Social API Post resource operations let you obtain information about posts and perform various operations on posts.

Table 8-1 provides a summary of the Post resource operations. Each operation is described in detail in the section that is listed.

These sections provide this information:

Purpose—Brief explanation of the operation

Availability—Cisco WebEx Social releases that support the operation

Request—HTTP method and URI for the operation

Request Payload—Description of the request payload, if the operation requires one

Response—Description of the expected response when the operation executes

Example—Sample request and response for the operation

Table 8-1 Post Resource Operations Summary 

Operation and Reference
Purpose

Get Information about a Post

Retrieves information about the designated post

Get Information about Posts

Retrieves information about one or more posts

Create a Post

Creates a new Cisco WebEx Social post

Update Information about a Post

Updates information about the designated post

Get Information about Attachments for a Post

Retrieve information about all attachments for the designated post

Add Attachments to a Post

Adds attachments to the designated post

Delete Attachments from a Post

Deletes all attachments from the designated post

Get Information about a Comment for a Post

Retrieves information about the designated comment for the designated post

Get Information about Comments for a Post

Retrieves information about the comments that have been added to the designated post

Create a Comment for a Post

Creates a comment for the designated post and adds the comment to the post

Update a Comment for a Post

Updates the designated comment for the designated post

Delete a Comment from a Post

Deletes the designated comment from the designated post

Add a Tag to a Post

Adds the designated tag to the designated post

Delete a Tag from a Post

Deletes the designated tag from the designated post

Get Information about a Video that is Embedded in a Post or Attached to a Micropost

Retrieves information about the video that is embedded in the designated TEXT type post or attached to the designated micropost, wall post, or community wall post

Attach an Video to a Micropost

Attaches the designated embedded video to the designated micropost, wall post, or community wall post

Update an Attached Video in a Micropost

Updates the embedded video in the designated micropost, wall post, or community wall post

Delete an Attached Video from a Micropost

Deletes the attached video from the designated micropost, wall post, or community wall post

Get Permissions for a Post

Retrieves the permissions that have been assigned to the designated post

Update Permissions for a Post

Updates permissions for the designated post

Get Users that have Marked a Designated Post as a Favorite

Retrieves Favorite resources that have as the destination the users that have marked the designated post as a favorite

Get Information about Users that Like a Designated Post

Retrieves Like resources that have as the destination the users that like the designated post

Get the Number of Users that Like a Designated Post

Retrieves the number of Like resources that have as the destination the users that like the designated post

Get Information about the Versions of a Post

Retrieves information about all versions of the designated post

Get the Differences Between Two Versions of a Post

Retrieves information about the differences between the two designated versions of a post

Restore an Older Version of a Post

Creates a new version of a post that contains the content of the designated version of that post

Get Information about All Activities that Relate to a Post

Retrieves information about all activities that relate to the designated post


Get Information about a Post

Purpose

Retrieves information about the designated post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

GET

{http|https}://server[:port]/api/quad/rest/posts/post_id[?query_parameters]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to retrieve detailed information. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

query_parameters—Query parameters. See the "Query Parameters" section for information about using query parameters. For this operation:

The fields query parameter is supported for selecting fields from the Post resource to include in a response (Table 3-37 describes these fields).

The filterBy query parameter is supported only with the version field in the Post resource.

The sortOrder query parameter does not apply.

The startIndex query parameter does not apply.

The count query parameter does not apply.

The meta query parameter is supported with the follow, like, favorite, and permissionflags values for requesting metadata.

The special query parameter readPost={true|false} designates whether the system marks a post as read when a client retrieves the post from the server.

The special query parameter filter=version:post_verion_id is supported for retrieving information only about the version of the post that is designated by post_verion_id. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with a response payload that can include one Post resource (the "Post Resource" section describes this resource).

Example

Request

GET http://webexsocialserver/api/quad/rest/posts/100001
Accept:application/json

Response

HTTP/1.1 200 OK
Content-Type: application/json
 
   

The response can also include the Post resource. For an example, see the "Post Resource Response, One Resource Returned" section.

Get Information about Posts

Purpose

Retrieves information about one or more posts.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

GET

{http|https}://server[:port]/api/quad/rest/posts/post_id[,...[post_id]]
[?query_parameters]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of a post about which to retrieve information. When specifying multiple identifiers, separate each one with a comma. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

query_parameters—Query parameters. See the "Query Parameters" section for information about using query parameters. For this operation:

The fields query parameter is supported for selecting fields from the Post resource to include in a response (Table 3-37 describes these fields)

The filterBy query parameter is not supported for filtering resources in a response

The sortOrder query parameter is not supported for sorting resources in a response

The startIndex query parameter is supported for paginating return results

The count query parameter is supported for designating the maximum number of items in the return results

The meta query parameter is supported with the follow, like, favorite, and permissionflags values for requesting metadata

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with a response payload that can include one or more Post resources (the "Post Resource" section describes this resource).

Example

Request
GET http://webexsocialserver/api/quad/rest/posts/100001,400005
Accept:application/json

Response

The response can also include the Post resource. For an example, see the "Post Resource Response, Multiple Resources Returned" section.

Create a Post

Purpose

Creates a new Cisco WebEx Social post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

POST

{http|https}://server[:port]/api/quad/rest/posts[?query_parameters]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

query_parameters—Query parameters. See the "Query Parameters" section for information about using query parameters. For this operation:

The fields query parameter is supported for selecting fields from the Post resource to include in a response (Table 3-37 describes these fields).

The filterBy query parameter is not supported for filtering resources in a response.

The sortOrder query parameter does not apply.

The startIndex query parameter does not apply.

The count query parameter does not apply.

The meta query parameter is supported with the like and the favorite values for requesting relationship metadata.

The special query parameter destUsers=user_id_1[,...[user_id_n]] is supported when the type field in the Post resource is MICRO. This parameter adds the new micropost to the walls of the users with the designated user identifiers. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section

The special query parameter destComm=community_id_1[,...[community_id_n]] is supported when the type field in the Post resource is MICRO. This query parameter adds the new micropost to the walls of the communities with the designated community identifiers. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

The special query parameter postExternal={true|false} is supported when the type field in the Post resource is MICRO. This query parameter designates whether the new micropost is added to an external application.

The special query parameter showOnProfile={true|false} is supported when the type field in the Post resource is TEXT. This query parameter designates whether a new post is added to the MyBlog page of all Cisco WebEx Social users.

Request Payload

The request payload includes fields from the Post resource (Table 3-37 describes these fields):

Required Fields
Optional Fields

title1
body2

defaultPermissions3
permissions
publicPost
question
tags
type4

1 Required for a TEXT type post. Optional for other post types.

2 Required for a MICRO type post. Optional for other post types.

3 If you do not include the defaultPermissions field, the post is created with comment and view permissions only.

4 If you do not specify a value for the type field, the post defaults to the TEXT type.


You can add an @mention to a micropost by including the following line in the payload when you create the micropost:

@[user_id, \"first_name last_name\", \"link\"]
 
   

Where:

user_id—Cisco WebEx Social identifier of the user to mention.

first_name—First name of the user to mention.

last_name—Last name of the user to mention.

link—Link to the Profile page of the user. For the standard Cisco WebEx Social user interface, enter this link in the format /web/user_id.

Response

Standard response (see the "API Responses" section) with a response payload that can include one Post resource (the "Post Resource" section describes this resource).

Example

Request
POST http://webexsocialserver/api/quad/rest/posts
Accept:application/json
Content-Type: application/json
{
 
   
    "title":"New Employee",
    "body":"Please welcome our new employee.",
    "type":"TEXT"
    "permissions": {
        "principal":{
            "id":"12345",
            "resource":"http://quad.cisco.com/schema/1.0/user"
        },
        "permissionFlags":{
            "view":"true",
            "edit":"false",
            "comment":"true",
            "share":"true",
            "authorize":"false"
        } },
    "tags":[{"name":"tag2"},{"name":"tag3"}, {"name":"tag4"}]
}

Response

HTTP/1.1 201 Created
Content-Type application/json
Location: http://webexsocialserver/api/quad/rest/posts/500001
 
   

The response can also include the Post resource. For an example, see the "Post Resource Response, One Resource Returned" section.

Update Information about a Post

Purpose

Updates information about the designated post.

You can use this operation to delete a post by setting the state field to DELETED in the request payload.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

PUT

{http|https}://server[:port]/api/quad/rest/posts/post_id[?query_parameters]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to update information. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

query_parameters—Query parameters. See the "Query Parameters" section for information about using query parameters. For this operation:

The fields query parameter is supported for selecting fields from the Post resource to include in a response (Table 3-37 describes these fields)

The filterBy query parameter is not supported for filtering resources in a response

The sortOrder query parameter does not apply

The startIndex query parameter does not apply

The count query parameter does not apply

The meta query parameter does not apply

Request Payload

The request payload includes fields from the Post resource (Table 3-37 describes these fields):

Required Fields
Optional Fields

attachments
body
defaultPermissions
permissions
publicPost
question
state1
tags
title

1 This operation supports values of ACTIVE and DELETED for the state field.


You can add an @mention to a micropost by including the following line in the payload when you update the micropost:

@[user_id, \"first_name last_name\", \"link\"]
 
   

Where:

user_id—Cisco WebEx Social identifier of the user to mention.

first_name—First name of the user to mention.

last_name—Last name of the user to mention.

link—Link to the Profile page of the user. For the standard Cisco WebEx Social user interface, enter this link in the format /web/user_id.

Response

Standard response (see the "API Responses" section) with an HTTP header only.

Example

Request

PUT http://webexsocialserver/api/quad/rest/posts/100001
Accept:application/json
Content-Type: application/json
 
   
{
   "body":"This text is the body of the post."
}

Response

HTTP/1.1 204 No Content

Get Information about Attachments for a Post

Purpose

Retrieve information about all attachments for the designated post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

GET

{http|https}://server[:port]/api/quad/rest/posts/post_id/attachments
[?query_parameters]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to retrieve information about attachments. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

query_parameters—Query parameters. See the "Query Parameters" section for information about using query parameters. For this operation:

The fields query parameter is supported for selecting fields from the Attachment resource to include in a response (Table 3-4 describes these fields)

The filterBy query parameter is not supported for filtering resources in a response

The sortOrder query parameter is not supported for sorting resources in a response

The startIndex query parameter is supported for paginating return results

The count query parameter is supported for designating the maximum number of items in the return results

The meta query parameter does not apply

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with a response payload that can include one or more Attachment resources (the "Attachment Resource" section describes this resource).

Example

Request

GET http://quadserver//api/quad/rest/posts/14/attachments
Accept:application/json

Response

HTTP/1.1 200 OK
Content-Length: 380
Content-Type: application/json
 
   
{ 
    "statusCode": 200, 
    "startIndex": 0, 
    "itemsPerPage": 1, 
    "totalResults": 0,
    "filtered": false, 
    "sorted": false, 
    "entry": [
        { 
            "data": { 
                "author": null, 
                "fileName": "322675-retro-apple-tv.jpg", 
                "id": 2310090, 
                "mimeType": "DOCUMENT", 
                "published": 1319673960078, 
                "resource": "", 
                "size": 27571, 
                "updated": 1319673960078, 
                "uri": "/c/post_action/get_attachment?postId=14&attachmentId=2310090"
            }
        }
    ], 
    "serverMessages": null
}

Add Attachments to a Post

Purpose

Adds attachments to the designated post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

POST

{http|https}://server[:port]/api/quad/rest/posts/post_id/attachments
[?fileName=filname]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to add attachments. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

filname—Name of a file that overrides the file that is specified in the request payload.

The fileName parameter is required if you are using Internet Explorer to send this API operation.

Request Payload

Attachment to be uploaded.

The HTTP Content-Type header must be multipart/form-data for this request. The form-data key must be specified as file=attachment_to_upload. If you are uploading a video, single-sign on (SSO) must be enabled in Cisco WebEx Social before you execute this operation.

Response

Standard response (see the "API Responses" section) with a response payload that can include one Attachment resource (the "Attachment Resource" section describes this resource).

Example

Request

POST http://webexsocialserver/api/quad/rest/posts/14/attachments
accept: application/json
content-length: 87899
 
   
expect: 100-continue
content-type: multipart/form-data; boundary=----------------------------02a4bb521c19
------------------------------02a4bb521c19
Content-Disposition: form-data; name="file"; filename="ProfilePhoto.jpg"
Content-Type: image/jpeg
<binary_file>
------------------------------02a4bb521c19--

Response

HTTP/1.1 201 Created
Content-Type: application/json
Location: http://webexsocialserver/api/quad/rest/posts/500001/attachments/2310090
 
   
{ 
    "statusCode": 200, 
    "startIndex": 0, 
    "itemsPerPage": 1, 
    "totalResults": 0,
    "filtered": false, 
    "sorted": false, 
    "entry": [
        { 
            "data": { 
                "author": null, 
                "fileName": "322675-retro-apple-tv.jpg", 
                "id": 2310090, 
                "mimeType": "DOCUMENT", 
                "published": 1319673960078, 
                "resource": "", 
                "size": 27571, 
                "updated": 1319673960078, 
                "uri": "/c/post_action/get_attachment?postId=14&attachmentId=2310090"
            }
        }
    ], 
    "serverMessages": null
}

Delete Attachments from a Post

Purpose

Deletes all attachments from the designated post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

DELETE

{http|https}://server[:port]/api/quad/rest/posts/post_id/attachments


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to delete attachments. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with an HTTP header only.

Example

Request

DELETE http://webexsocialserver/api/quad/rest/posts/14/attachments

Response

HTTP/1.1 200 OK

Get Information about a Comment for a Post

Purpose

Retrieves information about the designated comment for the designated post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

GET

{http|https}://server[:port]/api/quad/rest/posts/post_id/comments/comment_id
[?query_parameters]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to retrieve information about the comment. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

comment_id—Identifier of the comment to retrieve. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

query_parameters—Query parameters. See the "Query Parameters" section for information about using query parameters. For this operation:

The fields query parameter is supported for selecting fields from the PostComment resource to include in a response (Table 3-38 describes these fields)

The filterBy query parameter is not supported for filtering resources in a response

The sortOrder query parameter does not apply

The startIndex query parameter does not apply

The count query parameter does not apply

The meta query parameter does not apply

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with a response payload that can include one PostComment resource (the "PostComment Resource" section describes this resource).

Example

Request

GET http://webexsocialserver/api/quad/rest/posts/100001/comments/1234
Accept:application/json

Response

HTTP/1.1 200 OK
Content-Type: application/json
{
      "statusCode": 200, 
      "startIndex": 0, 
      "itemsPerPage": 1, 
      "totalResults": 0,
      "filtered": false, 
      "sorted": false, 
      "entry": [
            {
                  "data": {
                        "body": "comment1", 
                        "createDate": 1316789154239, 
                        "creator": {
                              "firstName": "Pat", 
                              "fullName": "Pat Kim", 
                              "id": 1234, 
                              "images": [ ], 
                              "jobTitle": "", 
                              "lastName": "Kim", 
                              "screenName": "patkim"
                        }, 
                        "id": 910001, 
                        "modifiedDate": 1316789154239, 
                        "parentMessageId": 310001, 
                        "replyCount": 0, 
                        "resource": "http://quad.cisco.com/schema/1.0/postcomment"
                  }
            }
      ], 
      "serverMessages": null
}

Get Information about Comments for a Post

Purpose

Retrieves information about the comments that have been added to the designated post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

GET

{http|https}://server[:port]/api/quad/rest/posts/post_id/comments
[?query_parameters]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to retrieve information about comments. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

query_parameters—Query parameters. See the "Query Parameters" section for information about using query parameters. For this operation:

The fields query parameter is supported for selecting fields from the PostComment resource to include in a response (Table 3-38 describes these fields)

The filterBy query parameter is not supported for filtering resources in a response

The sortOrder query parameter is not supported for sorting resources in a response

The startIndex query parameter is supported for paginating return results

The count query parameter is supported for designating the maximum number of items in the return results

The meta query parameter does not apply

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with a response payload that can include one or more PostComment resources (the "PostComment Resource" section describes this resource).

Example

Request

GET http://webexsocialserver/api/quad/rest/posts/400006/comments
Accept:application/json

Response

HTTP/1.1 200 OK
Content-Type: application/json
{
      "statusCode": 200, 
      "startIndex": 0, 
      "itemsPerPage": 1, 
      "totalResults": 0,
      "filtered": false, 
      "sorted": false, 
      "entry": [
            {
                  "data": {
                        "body": "comment1", 
                        "createDate": 1316789154239, 
                        "creator": {
                              "firstName": "Pat", 
                              "fullName": "Pat Kim", 
                              "id": 11234, 
                              "images": [ ], 
                              "jobTitle": "", 
                              "lastName": "Kim", 
                              "screenName": "patkim"
                        }, 
                        "id": 910001, 
                        "modifiedDate": 1316789154239, 
                        "parentMessageId": 310001, 
                        "replyCount": 0, 
                        "resource": "http://quad.cisco.com/schema/1.0/postcomment"
                  }
            },
           {
                  "data": {
                        "body": "comment1", 
                        "createDate": 1316789154239, 
                        "creator": {
                              "firstName": "Robin", 
                              "fullName": "Robin Smith", 
                              "id": 9876, 
                              "images": [ ], 
                              "jobTitle": "", 
                              "lastName": "Smith", 
                              "screenName": "RmbinSmith"
                        }, 
                        "id": 910002, 
                        "modifiedDate": 1316789154239, 
                        "parentMessageId": 310001, 
                        "replyCount": 0, 
                        "resource": "http://quad.cisco.com/schema/1.0/postcomment"
                  }
            }
], 
      "serverMessages": null
}

Create a Comment for a Post

Purpose

Creates a comment for the designated post and adds the comment to the post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

POST

{http|https}://server[:port]/api/quad/rest/posts/post_id/comments


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to create the comment. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

Request Payload

The request payload includes fields from the PostComment resource (Table 3-41 describes these fields):

Required Fields
Optional Fields

body


Response

Standard response (see the "API Responses" section) with a response payload that can include one PostComment resource (the "PostComment Resource" section describes this resource).

Example

Request

POST http://webexsocialserver/api/quad/rest/posts/400006/comments
Accept:application/json
Content-Type: application/json
{
    "body":"New Comment"
}

Response

HTTP/1.1 201 Created
Content-Type application/json
Location: http://webexsocialserver/api/quad/rest/posts/400006/comments/910001
 
   
{
      "statusCode": 200, 
      "startIndex": 0, 
      "itemsPerPage": 1, 
      "totalResults": 0,
      "filtered": false, 
      "sorted": false, 
      "entry": [
            {
                  "data": {
                        "body": "New comment", 
                        "createDate": 1316789154239, 
                        "creator": {
                              "firstName": "Pat", 
                              "fullName": "patkim",
                              "id": 1234, 
                              "images": [ ], 
                              "jobTitle": "", 
                              "lastName": "Kim", 
                              "screenName": "patkim"
                        }, 
                        "id": 910001, 
                        "modifiedDate": 1316789154239, 
                        "parentMessageId": 310001, 
                        "replyCount": 0, 
                        "resource": "http://quad.cisco.com/schema/1.0/postcomment"
                  }
            }
      ], 
      "serverMessages": null
}

Update a Comment for a Post

Purpose

Updates the designated comment for the designated post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

PUT

{http|https}://server[:port]/api/quad/rest/posts/post_id/comments/comment_id


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to update the comment. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

comment_id—Identifier of the comment to update. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

Request Payload

The request payload includes fields from the PostComment resource (Table 3-38 describes these fields):

Required Fields
Optional Fields

body


Response

Standard response (see the "API Responses" section) with an HTTP header only.

Example

Request

PUT http://webexsocialserver/api/quad/rest/posts/400006/comments/510138
Accept:application/json
Content-Type: application/json
{
 
   
    "body":"New Comment"
 
   
}

Response

HTTP/1.1 204 No Content

Delete a Comment from a Post

Purpose

Deletes the designated comment from the designated post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

DELETE

{http|https}://server[:port]/api/quad/rest/posts/post_id/comments/comment_id


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post from which to delete the comment. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

comment_id—Identifier of the comment to delete. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with an HTTP header only.

Example

Request

DELETE http://webexsocialserver/api/quad/rest/posts/400006/comments/510138

Response

HTTP/1.1 204 No Content

Add a Tag to a Post

Purpose

Adds the designated tag to the designated post.

For related information about tags, see Chapter 9 "Tags Resource and TagTrends Resource Operations."

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

POST

{http|https}://server[:port]/api/quad/rest/posts/post_id/tags


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. Required if the port number is not 80.

post_id—Cisco WebEx Social identifier of a post to which to add a tag. For information about obtaining the identifier that you need, see the ""Identifiers of Cisco WebEx Social Entities" section.

Request Payload

The request payload includes fields from the Tags resource (the "Tags Resource" section describes this resource)

Required Fields
Optional Fields

name


Response

Standard response (see the "API Responses" section) with an HTTP header only.

Example

Request

POST http://webexsocialserver/api/quad/rest/posts/9623/tags
Accept: application/json
Content-Type: application/json
{
    "name":"tag1"
}
 
   

Response

204 No Content

Delete a Tag from a Post

Purpose

Deletes the designated tag from the designated post.

For related information about tags, see Chapter 9 "Tags Resource and TagTrends Resource Operations."

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

DELETE

{http|https}://server[:port]/api/quad/rest/posts/post_id/tags/name


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. Required if the port number is not 80.

post_id—Cisco WebEx Social identifier of a post from which to delete a tag. For information about obtaining the identifier that you need, see the ""Identifiers of Cisco WebEx Social Entities" section.

name—Name of the tag to delete.

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with an HTTP header only.

Example

Request

DELETE http://webexsocialserver/api/quad/rest/posts/9623/tags/webex

Response

HTTP/1.1 204 No Content

Get Information about a Video that is Embedded in a Post or Attached to a Micropost

Purpose

Retrieves information about the video that is embedded in the designated TEXT type post or attached to the designated micropost, wall post, or community wall post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

GET

{http|https}://server[:port]/api/quad/rest/posts/post_id/embeddedvideos


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post or micropost for which to retrieve information about the attached or embedded video. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with a response payload that can include one or more EmbeddedVideo resource (the "EmbeddedVideo Resource" section describes this resource).

Example

Request

GET http://webexsocialserver/api/quad/rest/posts/100001/embeddedvideos
Accept:application/json

Response

HTTP/1.1 200 OK
Content-Type: application/json
{
   "statusCode":200,
   "startIndex":0,
   "itemsPerPage":1,
   "totalResults":-1,
   "filtered":false,
   "sorted":false,
   "entry":[
      {
         "data":{
            "html":"<a 
href=\"http://www.youtube.com/watch\">http://www.youtube.com/watch</a>",
            "id":0,
            "resource":"http://quad.cisco.com/schema/1.0/embeddedvideo",
            ""tag:"*[http://www.youtube.com/watch]"
         }
      }
   ],
   "serverMessages":null
}

Attach an Video to a Micropost

Purpose

Attaches the designated embedded video to the designated micropost, wall post, or community wall post. The video must come from an external video provider that is included in the external video providers white list. For more information, see the "Video Providers Resource Operations" section.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

POST

{http|https}://server[:port]/api/quad/rest/posts/post_id/embeddedvideos
?tag=*[
url[[,width,height]]|[,width,]|[, ,height]]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the micropost to which to attach the video. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

url—URL of the video to attach to the micropost.

width—Width of the video, in pixels. If you do not specify a width, the system uses the width that the template field in the VideoProviders resource defines.

height—Height of the video, in pixels. If you do not specify a height, the system uses the height that the template field in the VideoProviders resource defines

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with a response payload that can include one EmbeddedVideo resource (the "EmbeddedVideo Resource" section describes this resource).

Example

Request

POST http://webexsocialserver/api/quad/rest/posts/30200004/embeddedvideos 
?tag=*[http://www.youtube.com/watch?v=zSe-ZGoghA8]
Accept:application/json

Response

HTTP/1.1 201 Created
Content-Type application/json
{
  "statusCode" : 200,
  "startIndex" : 0,
  "itemsPerPage" : 1,
  "totalResults" : 1,
  "filtered" : false,
  "sorted" : false,
  "entry" : [ {
    "data" : {
      "html" : "<iframe width=\"560\" height=\"315\" 
src=\"http://www.youtube.com/embed/zSe-ZGoghA8\" frameborder=\"0\" 
allowfullscreen></iframe>",
      "id" : 0,
      "resource" : "http://quad.cisco.com/schema/1.0/embeddedvideo",
      "tag" : "*[http://www.youtube.com/watch?v=zSe-ZGoghA8]"
    }
  } ],
  "serverMessages" : null
}

Update an Attached Video in a Micropost

Purpose

Updates the embedded video in the designated micropost, wall post, or community wall post. The updated video must come from an external video provider that is included in the external video providers white list. For more information, see "Video Providers Resource Operations" section

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

PUT

{http|https}://server[:port]/api/quad/rest/posts/post_id//embeddedvideos
?tag=*[
url[[,width,height]]|[,width,]|[, ,height]]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the micropost for which to update the attached video. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

url—URL of the video to attach to the micropost.

width—Width of the video, in pixels. If you do not specify a width, the system uses the width that the template field in the VideoProviders resource defines.

height—Height of the video, in pixels. If you do not specify a height, the system uses the height that the template field in the VideoProviders resource defines

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with an HTTP header only.

Example

Request

PUT http://webexsocialserver/api/quad/rest/posts/1335/embeddedvideos? 
tag=*[http://www.youtube.com/watch?v=LkP5EJiPSC8, 640, 480]

Response

HTTP/1.1 204 No Content

Delete an Attached Video from a Micropost

Purpose

Deletes the attached video from the designated micropost, wall post, or community wall post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

DELETE

{http|https}://server[:port]/api/quad/rest/posts/post_id/embeddedvideos


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the micropost from which to delete the attached video. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with an HTTP header only.

Example

Request

DELETE http://webexsocialserver/api/quad/rest/posts/1357/embeddedvideos

Response

HTTP/1.1 204 No Content

Get Permissions for a Post

Purpose

Retrieves the permissions that have been assigned to the designated post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

GET

{http|https}://server[:port]/api/quad/rest/posts/post_id/permissions


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to retrieve permissions. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with a response payload that can include one Permission resource (the "Permission Resource" section describes this resource).

Example

Request

GET http://webexsocialserver/api/quad/rest/posts/14/permissions
Accept:application/json

Response

HHTTP/1.1 200 OK
Content-Type: application/json
{
    "statusCode": 200, 
    "startIndex": 0, 
    "itemsPerPage": 2, 
    "totalResults": 2, 
    "filtered": false, 
    "sorted": false, 
    "entry": [
        {
            "data": {
                "principal": {
                    "id": 310005, 
                    "resource": "http://quad.cisco.com/schema/1.0/community", 
                    "name": "test", 
                    "description": "asdf", 
                    "shortName": "/test1", 
                    "type": "open", 
                    "state": "live", 
                    "userCount": 1, 
                    "tags": [ ], 
                    "images": [ ]
                }, 
                "permissionFlags": {
                    "view": true, 
                    "edit": false, 
                    "comment": true, 
                    "share": false, 
                    "authorize": false
                }
            }
        }, 
        {
            "data": {
                "principal": {
                    "id": 310126, 
                    "resource": "http://quad.cisco.com/schema/1.0/user", 
                    "firstName": "user1", 
                    "lastName": "user1", 
                    "fullName": "user1 user1", 
                    "screenName": "user1"
                }, 
                "permissionFlags": {
                    "view": true, 
                    "edit": false, 
                    "comment": true, 
                    "share": false, 
                    "authorize": false
                }
            }
        }
    ], 
    "serverMessages": null
}

Update Permissions for a Post

Purpose

Updates permissions for the designated post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

PUT

{http|https}://server[:port]/api/quad/rest/posts/post_id/permissions


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to update permissions. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

Request Payload

The request payload includes fields from the Permission resource (Table 3-33 describes these fields):

Required Fields
Optional Fields

permissionFlags1

principal2

1 The permissionFlags field defines a resource that represents the status of permission types. All fields in this resource are required.

2 The principal field defines a resource that represents a Cisco WebEx Social user or a Cisco WebEx Social community. The id and the resource fields in this resource are required. Other fields are not used.


Response

Standard response (see the "API Responses" section) with an HTTP header only.

Example

Request

PUT http://webexsocialserver/api/quad/rest/posts/14/permissions
Accept:application/json
Content-Type: application/json
 
   
{
      "permission": {
            "principal": {
                  "id": "310126", 
                  "resource": "http://quad.cisco.com/schema/1.0/user"
            }, 
            "permissionFlags": {
                  "view": "true", 
                  "edit": "true", 
                  "comment": "true", 
                  "share": "true", 
                  "authorize": "true"
            }
      }
}

Response

HTTP/1.1 204 No Content

Get Users that have Marked a Designated Post as a Favorite

Purpose

Retrieves Favorite resources that have as the destination the users that have marked the designated post as a favorite.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

GET

{http|https}://server[:port]/api/quad/rest/posts/post_id/favorite
/@favoritedbyusers
[?query_parameters]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to retrieve the users that have marked is as a favorite. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

query_parameters—Query parameters. See the "Query Parameters" section for information about using query parameters. For this operation:

The fields query parameter is supported for selecting fields from the Favorite resource to include in a response (Table 3-26 describes these fields)

The filterBy query parameter is not supported for filtering resources in a response

The sortOrder query parameter is not supported for sorting resources in a response

The startIndex query parameter is supported for paginating return results

The count query parameter is supported for designating the maximum number of items in the return results

The meta query parameter is supported with the follow value for requesting relationship metadata

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with a response payload that can include one or more Favorite resources (the "Favorite Relationship Resource" section describes this resource).

Example

Request

GET http://webexsocialserver/api/quad/rest/posts/14/favorite/@favoritedbyusers
Accept:application/json

Response

HTTP/1.1 200 OK
Content-Type: application/json
 
   

The response can also include the Favorite resource. For an example, see the "Favorite Resource Response with User Resource in Destination Field, Multiple Resources Returned" section.

Get Information about Users that Like a Designated Post

Purpose

Retrieves Like resources that have as the destination the users that like the designated post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

GET

{http|https}://server[:port]/api/quad/rest/posts/post_id/like/@likersusers
[?query_parameters]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to retrieve the users that like it. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

query_parameters—Query parameters. See the "Query Parameters" section for information about using query parameters. For this operation:

The fields query parameter is supported for selecting fields from the Like resource to include in a response (Table 3-30 describes these fields)

The filterBy query parameter is not supported for filtering resources in a response

The sortOrder query parameter is not supported for sorting resources in a response

The startIndex query parameter is supported for paginating return results

The count query parameter is supported for designating the maximum number of items in the return results

The meta query parameter is supported with the follow value for requesting relationship metadata

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with a response payload that can include one or more Like resources (the "Like Relationship Resource" section describes this resource).

Example

Request

GET http://webexsocialserver/api/quad/rest/posts/14/like/@likersusers
Accept:application/json

Response

HTTP/1.1 200 OK
Content-Type: application/json
 
   

The response can also include the Like resource. For an example, see the "Like Resource Response with User Resource in Destination Field, Multiple Resources Returned" section.

Get the Number of Users that Like a Designated Post

Purpose

Retrieves the number of Like resources that have as the destination the users that like the designated post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

HEAD

{http|https}://server[:port]/api/quad/rest/posts/post_id/like/@likersusers
[?query_parameters]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to retrieve the number of users that like it. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

query_parameters—Query parameters. See the "Query Parameters" section for information about using query parameters. For this operation:

The fields query parameter does not apply

The filterBy query parameter is not supported for filtering resources in a response

The sortOrder query parameter does not apply

The startIndex query parameter does not apply

The count query parameter does not apply

The meta query parameter does not apply

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with an HTTP header only. The response includes the count of users that have indicated that they like the designated post.

Example

Request

HEAD http://webexsocialserver/api/quad/rest/posts/14/like/@likersusers

Response

HTTP/1.1 204 No Content
x-quad-count: 2

Get Information about the Versions of a Post

Purpose

Retrieves information about all versions of the designated post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

GET

{http|https}://server[:port]/api/quad/rest/posts/post_id/postversions
[&query_parameters]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to obtain version history. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

query_parameters—Query parameters. See the "Query Parameters" section for information about using query parameters. For this operation:

The fields query parameter is supported for selecting fields from the PostVersion resource to include in a response (Table 3-38 describes these fields)

The filterBy query parameter is not supported for filtering resources in a response

The sortOrder query parameter is not supported for sorting resources in a response

The startIndex query parameter is not supported for paginating return results

The count query parameter is not supported for designating the maximum number of items in the return results

The meta query parameter does not apply

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with a response payload that can include one or more PostVersion resources (the "PostVersion Resource" section describes this resource).

Examples

Request

GET http://webexsocialserver/api/quad/rest/posts/13487/postversions
Accept: application/json 

Response

HTTP/1.1 200 OK
Content-Type: application/json 
{
     "statusCode": 200,
     "startIndex": 0,
     "itemsPerPage": 1,
     "totalResults": 1,
     "filtered": false,
     "sorted": false,
     "entry": [
         {
             "data": {
                 "action": "Original Post:Test postversion",
                 "createDate": 1370496032021,
                 "creator": {
                     "firstName": "Kim",
                     "fullName": "Kim Jones",
                     "id": 9710002,
                     "images": null,
                     "jobTitle": "Manager",
                     "lastName": "Jones",
                     "resource": "http://quad.cisco.com/schema/1.0/user",
                     "screenName": "kjones",
                     "status": "ACTIVE"
                 },
                 "id": 1,
                 "note": "Test postversion",
                 "resource": "http://quad.cisco.com/schema/1.0/postversion"
             }
         }
     ],
     "serverMessages": null
 }

Get the Differences Between Two Versions of a Post

Purpose

Retrieves information about the differences between the two designated versions of a post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

GET

{http|https}://server[:port]/api/quad/rest/posts/post_id/postversiondiff/
post_version_(1):post_version_(2)


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to compare version differences. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

post_version_(1), post_version_(2)—Versions of the post to compare. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with a response payload that can include one PostVersionDiff resource (the "PostVersionDiff Resource" section describes this resource).

Examples

Request

GET http://webexsocialserver/api/quad/rest/posts/13487/postversiondiff/3:1
Accept: application/json 

Response

HTTP/1.1 200 OK
Content-Type: application/json 
{
     "statusCode": 200,
     "startIndex": 0,
     "itemsPerPage": 1,
     "totalResults": 1,
     "filtered": false,
     "sorted": false,
     "entry": [
         {
             "data": {
                 "body": "<?xml version=\"1.0\" encoding=\"UTF-8\"?><div> 
asdf</div><div><span class=\"diff-html-added\" previous=\"first-diff\" 
changeId=\"added-diff-0\" next=\"last-diff\"> </span><span class=\"diff-html-added\" 
id=\"added-diff-0\" previous=\"first-diff\" changeId=\"added-diff-0\" 
next=\"last-diff\">edit 1</span></div>",
                 "resource": "http://quad.cisco.com/schema/1.0/postversiondiff"
             }
         }
     ],
     "serverMessages": null
 }

Restore an Older Version of a Post

Purpose

Creates a new version of a post that contains the content of the designated version of that post.

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

PUT

{http|https}://server[:port]/api/quad/rest/posts/post_id/
?restoreFromVersion=
post_version


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to restore an older version. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

post_version—Older version of the post that contains the content to be included in the new post. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with an HTTP header only.

Examples

Request

PUT http://webexsocialserver/api/quad/rest/posts/13487/?restoreFromVersion=1
Content-Type: application/json
Accept: application/json 

Response

HTTP/1.1 204 No Content

Get Information about All Activities that Relate to a Post

Purpose

Retrieves information about all activities that relate to the designated post.

An activity consists of these components: actor, action, object, and target. An activity describes an action that is performed by an actor with or on an object that relates to a target. For example, an actor could be a Cisco WebEx Social user, an action could be "created," an object could be a document, and a target could be a library.

A component may be explicit or implied. For example, an activity could be described as "Nicole updated a document in her library" or "Mike shared a post."

Availability

Cisco WebEx Social 3.4 and later.

Request

HTTP Method
URI

GET

{http|https}://server[:port]/api/quad/rest/posts/post_id}/activities
[?query_parameters]


where:

server—Host name or IP address of the Cisco WebEx Social server.

port—Port number on which the Cisco WebEx Social server listens for API requests. The default value is 80.

post_id—Identifier of the post for which to retrieve related activities. For information about obtaining the identifier that you need, see the "Identifiers of Cisco WebEx Social Entities" section.

query_parameters—Query parameters. See the "Query Parameters" section for information about using query parameters. For this operation:

The fields query parameter does not apply.

The filterBy query parameter is not supported for filtering resources in a response.

The sortOrder query parameter is not supported for sorting resources in a response.

The startIndex query parameter is not supported for paginating return results.

The count query parameter is supported for designating the maximum number of items in the return results. The system retrieves activities in reverse chronological order.

The meta query parameter does not apply.

Request Payload

A request payload is not required.

Response

Standard response (see the "API Responses" section) with a response payload that includes the following:

Item
Explanation

objectType

Appears as collection.

timestamp

Date and time that the earliest activity that is returned occurred, in UTC format.

totalItems

Total number of items that are returned.

items

Array of Activity activities resources. The "Activity Activities Resource" section describes this resource.


Example

Request

GET http://webexsocialserver/api/quad/rest/posts/600001/activities
Accept:application/json

Response

HTTP/1.1 200 OK
Content-Type: application/json
 
   

The response can also include the Collection activities resource. For an example, see the "Collection Activities Resource Response" section.