Approve Member Media

From KickApps Documentation

Jump to: navigation, search

Contents

Overview

The Approve Member Media call lets you approve community media that was uploaded by your community members. Use the Reject Member Media call to reject member media.

Note:The approve media API call behaves in the same exact way as the AC manage media functionality except that no emails will be sent to members when their media is approved.

URI

Your request will look something like the following:

http://api.kickapps.com/rest/media/approve/{mediaType}/{mediaId}/{as}

Parameters

  • mediaType. The media type of the media that is being approved. Possible values are: audio, video, blogs, sets, photo and page.
  • mediaId. The id of media that is being approved.
  • as. The site id to search. AS is unique for each of the affiliate site.

Post Parameters

  • t. String. Required. Your access permissions.
  • callback. String. Optional. The name of your JavaScript callback function.
  • clientIP. String. Optional. Use the clientIP parameter to pass the IP address of the user making the call. If the IP has been blocked by the webmaster under the Affiliate Center -> Manage Members section, an error message will be returned starting with "status":"-1","error":"This IP address has been banned".

Payload

On success, a return that begins with "status":"1","message":"Media approved successfully.".

If media is still being transcoded or processed an error that begins with "status":"-1","message":" Media is currently being processed. Please try again later." will be returned.

If media is deleted an error that begins with "status":"-1","message":"media not found. Please check the information provided." will be returned.

If mediaId and as do not match then an error that begins with "status":"-1","message":" Media does not exist." will be returned.

Permissions

Overview

KickConnect API call that lets you post activities done outside the community into the community activity feeds for members.

Your request will look something like the following:

http://api.kickapps.com/rest/kickconnect/{memberId}/{as} 

Parameters

As shown above, your call will include the following parameters:

  • memberId. The id of the user for who the update is being made.
  • as. The site Id to search. as is unique for each of the affiliate's sites.

Post Parameters

  • t. String. Required. Your access permissions.
  • callback. String. Optional. The name of your JavaScript callback function.
  • clientIP. String. Optional. Use the clientIP parameter to pass the IP address of the user making the call. If the IP has been blocked by the webmaster under the Affiliate Center -> Manage Members section, an error message will be returned starting with "status":"-1","error":"This IP address has been banned".
  • storyContent. Required. Accepts HTML and text. Allows 5,000 characters. Be sure to urlEncode the string that you pass for this variable.
  • storyIcon. Optional. url of the image to be associated with the story. Recommended size is 16 X 16.
  • postedFromSource. Optional. This is the name of the service from which the activity is being posted from. Allows 200 characters.
  • postToGroups. Optional. Should accept comma separated groupID's. Should only post to a group if the user is a member of that group.

JSON Payload

  • On success, the call will return "status":"1","message":"Story published successfully."
  • On failure, the call will return "status":"-1","message":"Story could not be published. Please make sure that the provided information is accurate."
  • If the user doesn't belong to the group(s) return, "status":"-1","message":"Story could not be published. Please make sure that the member belongs to the group(s)."

Permissions

List of KickApps API Calls


Note: Occasionally (and without advanced warning) we modify our API calls by adding new parameters in the response payload. Please keep this in mind when designing your strategy for parsing our responses.