Member Favorite Media Check
From KickApps Documentation
Contents |
Overview
This call enables you to check if a member has favorited a media. If the user has favorited the media the call will return "true". if the user has not favorited the media the call will return "false"
Your request will look something like the following:
http://api.kickapps.com/rest/check/favorite/{mediaType}/{mediaId}/{as}
Parameters
As shown above, your call will include the following parameters:
- mediaType. string. Media type of the media for which you want to perform the check. Supported media types: audio, blog, emedia, photo, video, sets.
- mediaId. integer. Media id of the media for which you want to perform the check.
- as. integer. The site that this media id is associated with. 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".
- userId. integer. optional. An affiliate/editor can pass the userId of the member for whom he wants to perform this check.If the webmaster/editor does not pass an additional userId the call will do the check for the affiliate/editor account.
- url. string. Required if the media type passed is emedia
Payload
If the user has favorited the media the following payload is returned:
{"payload_type":"json","isFavorite":"true","status":"1","error":""}
If the user has not favorited the media the following payload is returned:
{"payload_type":"json","isFavorite":"false","status":"1","error":""}
On error where a user does not exist, a payload that begins with status":"-1","error":"The user does not exist."
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.
Favorites






