MySpace Open Platform: Documentation Wiki - Recent changes [en]

OpenSocial v0.9 People

2009-11-24T17:58:10Z

Base URI:

←Older revision		Revision as of 17:58, 24 November 2009
Line 1:		Line 1:
	==Base URI==		==Base URI==
-	The base ~~uri~~ for ~~Activities~~ on MySpace is http://opensocial.myspace.com/roa/09/people. This endpoint supports GETs~~, PUTs and POSTs~~. ~~A user can only update their own information.~~	+	The base URI for People on MySpace is http://opensocial.myspace.com/roa/09/people. This endpoint supports GETs.

	==URI Parameters==		==URI Parameters==

Open Search

2009-11-20T04:14:10Z

MySpace Search 1.0 videos sample xml

2009-11-20T04:08:03Z

New page: <source lang="xml"> <?xml version="1.0"?> <response xmlns="http://ns.opensocial.org/2008/opensocial"> <startIndex>1</startIndex> <itemsPerPage>10</itemsPerPage> <totalResults>30</to...

New page

<source lang="xml">

<?xml version="1.0"?>
<response xmlns="http://ns.opensocial.org/2008/opensocial">
<startIndex>1</startIndex>
<itemsPerPage>10</itemsPerPage>
<totalResults>30</totalResults>
<resultCount>10</resultCount>
<searchId>3fda3345-8872-4372-a635-72c34ad06641</searchId>
<entry>
<id>myspace.com.mediaItem.video.27701959</id>
<displayName>Tonio! A&B</displayName>
<profileUrl>http://www.myspace.com/chito_chevy</profileUrl>
<thumbnailUrl>http://c3.ac-images.myspacecdn.com/images01/24/s_9cd2b761e169fbf39d9b7594a66c7ef2.jpg</thumbnailUrl>
<videoId>949266</videoId>
<videoUrl>http://vids.myspace.com/index.cfm?fuseaction=vids.individual&videoid=949266&searchid=3fda3345-8872-4372-a635-72c34ad06641</videoUrl>
<videoChannelUrl>http://vids.myspace.com/index.cfm?fuseaction=vids.channel&ContributorID=27701959&searchid=3fda3345-8872-4372-a635-72c34ad06641</videoChannelUrl>
<videoThumbnailUrl>http://b4.ac-images.myspacecdn.com/00721/47/29/721409274_thumb1.jpg</videoThumbnailUrl>
<title>test</title>
<isOfficial>0</isOfficial>
<description>1000 watt 10 1/2 in" subs</description>
<categories />
<tags />
<duration>00:29</duration>
<rating>0</rating>
<numViews>636</numViews>
<numComments>2</numComments>
</entry>
<entry>
<id>myspace.com.mediaItem.video.</id>
<displayName>+.:.cHiNiTa.:.+</displayName>
<profileUrl>http://www.myspace.com/moocowkillakrew</profileUrl>
<thumbnailUrl>http://c1.ac-images.myspacecdn.com/images01/65/s_d787b81e3cd5054ec81ebfba103c7860.jpg</thumbnailUrl>
<videoId>1557266</videoId>
<videoUrl>http://vids.myspace.com/index.cfm?fuseaction=vids.individual&videoid=1557266&searchid=3fda3345-8872-4372-a635-72c34ad06641</videoUrl>
<videoChannelUrl>http://vids.myspace.com/index.cfm?fuseaction=vids.channel&ContributorID=27422601&searchid=3fda3345-8872-4372-a635-72c34ad06641</videoChannelUrl>
<videoThumbnailUrl>http://b1.ac-images.myspacecdn.com/00873/17/07/873357071_thumb1.jpg</videoThumbnailUrl>
<title>Test</title>
<isOfficial>0</isOfficial>
<description>Ha-Ha</description>
<categories />
<tags />
<duration>01:49</duration>
<rating>0</rating>
<numViews>17</numViews>
<numComments>0</numComments>
</entry>
…
<entry>
<id>myspace.com.mediaItem.video.26550012</id>
<displayName>Pat</displayName>
<profileUrl>http://www.myspace.com/26550012</profileUrl>
<thumbnailUrl>http://x.myspacecdn.com/images/no_pic.gif</thumbnailUrl>
<videoId>31919936</videoId>
<videoUrl>http://vids.myspace.com/index.cfm?fuseaction=vids.individual&videoid=31919936&searchid=3fda3345-8872-4372-a635-72c34ad06641</videoUrl>
<videoChannelUrl>http://vids.myspace.com/index.cfm?fuseaction=vids.channel&ContributorID=26550012&searchid=3fda3345-8872-4372-a635-72c34ad06641</videoChannelUrl>
<videoThumbnailUrl>http://d4.ac-videos.myspacecdn.com/videos02/26/thumb1_eba6dbf6bab8b23015aa5eb441a4cbb7.jpg</videoThumbnailUrl>
<title>test</title>
<isOfficial>0</isOfficial>
<description>test</description>
<categories>
<category>
<name>User Videos</name>
<value>http://vids.myspace.com/index.cfm?fuseaction=vids.charts&category=1&searchid=3fda3345-8872-4372-a635-72c34ad06641</value>
</category>
<category>
<name>TV Show or Movie</name>
<value>http://vids.myspace.com/index.cfm?fuseaction=vids.charts&category=2&searchid=3fda3345-8872-4372-a635-72c34ad06641</value>
</category>
</categories>
<tags>
<tag>
<name>test</name>
<value>http://local-opensocial.myspace.com/opensearch?format=xml&queryType=videos&searchTerms=test&tag=1</value>
</tag>
</tags>
<duration>00:39</duration>
<rating>0</rating>
<numViews>1</numViews>
<numComments>0</numComments>
</entry>
</response>

</source>

MySpace Search 1.0 videos sample json

2009-11-20T04:07:42Z

New page: <source lang="javascript"> { "startIndex" : "1", "itemsPerPage" : "10", "totalResults" : "30", "resultCount" : "10", "searchId" : "6064b888-d9d6-4839-adc5-40884b9129a...

New page

<source lang="javascript">

{
"startIndex" : "1",
"itemsPerPage" : "10",
"totalResults" : "30",
"resultCount" : "10",
"searchId" : "6064b888-d9d6-4839-adc5-40884b9129a8",
"entry" : [ {
"id" : " myspace.com.mediaItem.video.27701959",
"displayName" : "Tonio! A&B",
"profileUrl" : "http://www.myspace.com/chito_chevy",
"thumbnailUrl" : "http://c3.ac-images.myspacecdn.com/images01/24/s_9cd2b761e169fbf39d9b7594a66c7ef2.jpg",
"videoId" : "949266",
"videoUrl" : "http://vids.myspace.com/index.cfm?fuseaction=vids.individual&videoid=949266&searchid=6064b888-d9d6-4839-adc5-40884b9129a8",
"videoChannelUrl" : "http://vids.myspace.com/index.cfm?fuseaction=vids.channel&ContributorID=27701959&searchid=6064b888-d9d6-4839-adc5-40884b9129a8",
"videoThumbnailUrl" : "http://b4.ac-images.myspacecdn.com/00721/47/29/721409274_thumb1.jpg",
"title" : "test",
"isOfficial" : "0",
"description" : "1000 watt 10 1/2 in\" subs",
"categories" : [ ],
"tags" : [ ],
"duration" : "00:29",
"rating" : "0",
"numViews" : "636",
"numComments" : "2"
},
…
{
"id" : "myspace.com.mediaItem.video.26550012",
"displayName" : "Pat",
"profileUrl" : "http://www.myspace.com/26550012",
"thumbnailUrl" : "http://x.myspacecdn.com/images/no_pic.gif",
"videoId" : "31919936",
"videoUrl" : "http://vids.myspace.com/index.cfm?fuseaction=vids.individual&videoid=31919936&searchid=6064b888-d9d6-4839-adc5-40884b9129a8",
"videoChannelUrl" : "http://vids.myspace.com/index.cfm?fuseaction=vids.channel&ContributorID=26550012&searchid=6064b888-d9d6-4839-adc5-40884b9129a8",
"videoThumbnailUrl" : "http://d4.ac-videos.myspacecdn.com/videos02/26/thumb1_eba6dbf6bab8b23015aa5eb441a4cbb7.jpg",
"title" : "test",
"isOfficial" : "0",
"description" : "test",
"categories" : [ {
"name" : "User Videos",
"value" : "http://vids.myspace.com/index.cfm?fuseaction=vids.charts&category=1&searchid=6064b888-d9d6-4839-adc5-40884b9129a8"
}, {
"name" : "TV Show or Movie",
"value" : "http://vids.myspace.com/index.cfm?fuseaction=vids.charts&category=2&searchid=6064b888-d9d6-4839-adc5-40884b9129a8"
} ],
"tags" : [ {
"name" : "test",
"value" : "http://local-opensocial.myspace.com/opensearch?format=json&queryType=videos&searchTerms=test&tag=1"
} ],
"duration" : "00:39",
"rating" : "0",
"numViews" : "1",
"numComments" : "0"
} ]
}

</source>

MySpace Search 1.0 images sample xml

2009-11-20T04:07:21Z

New page: <source lang="xml"> <?xml version="1.0"?> <response xmlns="http://ns.opensocial.org/2008/opensocial"> <startIndex>1</startIndex> <itemsPerPage>10</itemsPerPage> <totalResults>35</to...

New page

MySpace Search 1.0 images sample json

2009-11-20T04:06:57Z

New page: <source lang="javascript"> { "startIndex" : "1", "itemsPerPage" : "10", "totalResults" : "35", "resultCount" : "5", "searchId" : "28641320-539f-4340-b070-2936998925fd...

New page

<source lang="javascript">

{
"startIndex" : "1",
"itemsPerPage" : "10",
"totalResults" : "35",
"resultCount" : "5",
"searchId" : "28641320-539f-4340-b070-2936998925fd",
"entry" : [ {
"id" : "myspace.com.mediItem.image.26911917",
"displayName" : "TIFFANY",
"profileUrl" : "http://www.myspace.com/savannahgurl_85",
"thumbnailUrl" : "http://c3.ac-images.myspacecdn.com/images01/93/m_e58644888fae85e9106de3cce54f89d2.jpg",
"imageId" : "31361691",
"imageUrl" : "http://web.myspace.dev/index.cfm?fuseaction=viewImage&friendID=26911917&imageID=31361691",
"albumUrl" : "http://web.myspace.dev/index.cfm?fuseaction=user.viewAlbums2&friendID=26911917&view=true"
},
…
{
"id" : "myspace.com.mediaItem.image.26369269",
"displayName" : "~*~Jeannette~*~",
"profileUrl" : "http://www.myspace.com/devilwhiterose",
"thumbnailUrl" : "http://c4.ac-images.myspacecdn.com/images01/96/m_ed62eb0e6e1c7b2e2a4a0c3d15edbc7b.jpg",
"imageId" : "31361287",
"imageUrl" : "http://web.myspace.dev/index.cfm?fuseaction=viewImage&friendID=26369269&imageID=31361287",
"albumUrl" : "http://web.myspace.dev/index.cfm?fuseaction=user.viewAlbums2&friendID=26369269&view=true"
} ]
}

</source>

MySpace Search 1.0 people sample xml

2009-11-20T04:06:34Z

New page: <source lang="xml"> <?xml version="1.0"?> <response xmlns="http://ns.opensocial.org/2008/opensocial"> <startIndex>1</startIndex> <itemsPerPage>10</itemsPerPage> <totalResults>500</t...

New page

MySpace Search 1.0 people sample json

2009-11-20T04:06:16Z

New page: <source lang="javascript"> { "startIndex" : "1", "itemsPerPage" : "10", "totalResults" : "500", "resultCount" : "10", "searchId" : "60f4b61c-501d-42fa-9419-88209771ab...

New page

<source lang="javascript">

{
"startIndex" : "1",
"itemsPerPage" : "10",
"totalResults" : "500",
"resultCount" : "10",
"searchId" : "60f4b61c-501d-42fa-9419-88209771abea",
"entry" : [ {
"id" : "myspace.com.person.395438066",
"displayName" : "The Car",
"profileUrl" : "http://www.myspace.com/395438066",
"thumbnailUrl" : "http://x.myspacecdn.com/images/no_pic.gif",
"msUserType" : "RegularUser",
"gender" : "Male",
"age" : "109",
"sexualOrientation" : "No Answer",
"lookingFor" : "",
"location" : "BEVERLY HILLS, California",
"updated" : "7/9/2008 5:17:00 PM"
},
…
{
"id" : "myspace.com.person.509347",
"displayName" : "CAR",
"profileUrl" : "http://www.myspace.com/509347",
"thumbnailUrl" : "http://b2.ac-images.myspacecdn.com/00109/27/14/109104172_s.jpg",
"msUserType" : "RegularUser",
"gender" : "Male",
"age" : "25",
"sexualOrientation" : "Straight",
"lookingFor" : "Networking, Dating, Serious Relationships, Friends",
"location" : "Maple Grove, Minnesota",
"updated" : "5/24/2009 9:36:00 PM"
} ]
}

</source>

Open Search

2009-11-20T04:01:54Z

New page: Category:Early Adopters ==Base URI== The base uri for OpenSearch on MySpace is http://api.myspace.com/opensearch Each individual search url endpoint is as follow: <ul> <li>http://api....

New page

[[Category:Early Adopters]]
==Base URI==
The base uri for OpenSearch on MySpace is http://api.myspace.com/opensearch
Each individual search url endpoint is as follow:

<ul>
<li>http://api.myspace.com/opensearch/people</li>
<li>http://api.myspace.com/opensearch/images</li>
<li>http://api.myspace.com/opensearch/videos</li>

<li>TBD: http://api.myspace.com/opensearch/{music}</li>
<li>TBD: http://api.myspace.com/opensearch/local</li>
</ul>

For OpenSearch Description Document: GET http://api.myspace.com/opensearch

==Description==

This endpoint allows developers to search for people, videos, images, music, and local. These endpoints are meant to function much like sitesearch.
Its also meant to be compatible with OpenSocial with the response format.

This API allows you to:
* Search for MySpace users
* Search for images on MySpace
* Search for Official videos and Music Videos
* TBD: Search for music, artists, songs, albums
* TBD: Search for Local data and reviews
* Allow the same functionality as sitesearch
http://searchservice.myspace.com/index.cfm?fuseaction=sitesearch.results&orig=search_Header&origpfc=Splash&type=People&qry=car&submit=Search

==Supported HTTP Protocols==
* GET
==Supported Input and Response Types==
* XML
* JSON

==More Documents on Search==

* [[MySpace_Search_Spec_1.0 | MySpace Search Spec 1.0]]
* [[MySpace_OpenSearch_Extension_1.0 | MySpace OpenSearch Extension 1.0]]

==Examples of Search==

* [[MySpace_Search_1.0_people_sample_json | People JSON Example]]
* [[MySpace_Search_1.0_people_sample_xml | People XML Example]]
* [[MySpace_Search_1.0_images_sample_json | Images JSON Example]]
* [[MySpace_Search_1.0_images_sample_xml | Images XML Example]]
* [[MySpace_Search_1.0_videos_sample_json | Videos JSON Example]]
* [[MySpace_Search_1.0_videos_sample_xml | Videos XML Example]]

==QueryString Parameters==
The OpenSearch URI accepts querystring parameters as part of the URI.
Below is a list of required and optional parameters broken by the type of search.

=== http://api.myspace.com/opensearch/people ===
====Required Parameters====
* searchTerms - Free form search terms or query words (required) [ex. searchTerms=car]
====Optional Parameters====
* format - Response format type [ex. format=json or format=xml]
* count - Number of items to return [ex. count=10]
* startPage - Which page to start at for the results [ex. startPage=1]
* culture - The culture context of the search; for instance japan is ja-jp; default is en-us [ex. culture=en-us]

* searchBy - Which field the search should go through. Default is all the fields (yomi is only available to ja-jp culture) [ex. searchBy=name or searchBy=displayname or searchBy=email or searchBy=yomi]
* gender - The gender to filter on; default is no preference or both [ex. gender=m or gender=f]
* hasPhoto - Filter for those who only has photo; default is either [ex. hasPhoto=on]
* minAge - Minimum age to start the search (same filter as site search) [ex. minAge=18]
* maxAge - Maximum age to end the search with (same filter as site search) [ex. maxAge=68]
* location - The location field such as city state and country to search for [ex. location=US]
* distance - Distance away from location to return results; default is miles; depending on culture passed in it can be kilometers [ex. distance=25]
* latitude - geo latitude to search; combination with longitude required when used [ex. latitude=1]
* longitude - geo longtitude to search; combination with latitude is required when used [ex. longitude=1]
* regionId - regionId to search with [ex. regionId=1]
* countryId - countryId to search with [ex. countryId=1]
* countryCode - countryCode to search with [ex. countryCode=US]

=== http://api.myspace.com/opensearch/images ===
====Required Parameters====
* searchTerms - Free form search terms or query words (required) [ex. searchTerms=car]
====Optional Parameters====
* format - Response format type [ex. format=json or format=xml]
* count - Number of items to return [ex. count=10]
* startPage - Which page to start at for the results [ex. startPage=1]
* culture - The culture context of the search; for instance japan is ja-jp; default is en-us [ex. culture=en-us]

* sortBy - Ways to sort the images; when excluded sortBy is all [ex. sortBy=popular or sortBy=recent]
* sortOrder - Order of the image sorting which can be descending (default) or ascending [ex. sortOrder=asc]

=== http://api.myspace.com/opensearch/videos ===
====Required Parameters====
* searchTerms - Free form search terms or query words (required) [ex. searchTerms=car]
====Optional Parameters====
* format - Response format type [ex. format=json or format=xml]
* count - Number of items to return [ex. count=10]
* startPage - Which page to start at for the results [ex. startPage=1]
* culture - The culture context of the search; for instance japan is ja-jp; default is en-us [ex. culture=en-us]

* tag - Determine if this is a tag search [ex. tag=1]
* videoMode - Determine if this is a tag search [ex. videoMode=1 (music videos) or videoMode=2 (official)]

== Authentication ==

Consumer of these APIs can use OAuth 1.0a to access the search endpoints.
An access token is not required.
http://oauth.net/core/1.0a

Real Time Stream Functional Overview

2009-11-20T03:54:56Z

←Older revision		Revision as of 03:54, 20 November 2009
Line 1:		Line 1:
	[[Category:Early Adopters]]		[[Category:Early Adopters]]
-
	__NOTOC__		__NOTOC__
-
	==Overview==		==Overview==
	MySpace will soon be launching a new set of APIs and functionality to provide the stream of user activities in real time (aka Real Time Stream). The new functionality exposes the activity stream via a subscription-push model.		MySpace will soon be launching a new set of APIs and functionality to provide the stream of user activities in real time (aka Real Time Stream). The new functionality exposes the activity stream via a subscription-push model.

Special:Log/upload

2009-11-20T03:54:38Z

uploaded "Image:ActivitySubscriptionFlow.png"

Real Time Stream Functional Overview

2009-11-20T03:53:53Z

New page

[[Category:Early Adopters]]

__NOTOC__

==Overview==
MySpace will soon be launching a new set of APIs and functionality to provide the stream of user activities in real time (aka Real Time Stream). The new functionality exposes the activity stream via a subscription-push model.

Product branding for this new functionality is still pending. Internally this is known at the Flood API.

==Activity Subscription Flow==
# An application external to MySpace invokes the Subscription endpoint to create an Activity Stream Subscription. The subscription parameters include filtering criteria and partner endpoint URL which should receive the stream.
# As activities are triggered on MySpace, they are filtered based on the criteria in the subscription and optionally sampled (for rate limiting) and batched.
# The stream is then pushed to the partner endpoint for application consumption.

[[Image:ActivitySubscriptionFlow.png]]

==Reference Information==
* [http://developerwiki-stage/index.php?title=Stream_Subscription_API Activity Stream Subscription Endpoint Documentation]
* [http://wiki.developer.myspace.com/index.php?title=Category:ActivityStreams Activity Streams Reference]
* [http://wiki.developer.myspace.com/index.php?title=Standards_for_Activity_Streams Standards for Activity Streams]

''Note: In the future, MySpace is planning to implement PubSubHubBub mechanisms for specific activity streams. More information on this topic will be available very soon.''

==Next Steps for Partners and Developers==
# If not done previously, sign up for a Developers account via http://developer.myspace.com/Modules/Apps/Pages/ApplyDevSandbox.aspx
# Register/create your application via http://developer.myspace.com/Modules/Apps/Pages/CreateAppAccount.aspx
# Set up your endpoint to receive the activity stream
# Invoke the Subscription endpoint to subscribe to activities you would like to receive
# Receive and consume the activity stream which will be pushed to your endpoint

Commenting on Status and Mood

2009-11-20T03:48:14Z

New page

[[Category:Early Adopters]]

==Base URI==
The base URI for statusMoodComments on MySpace is http://opensocial.myspace.com/roa/09/statusmoodcomments. This endpoint currently supports GET and POST.

==URI Parameters==
Parameters are accepted as part of the URI. URIs are of the following forms:
This url as a GET will return all the comments.
* http://opensocial.myspace.com/roa/09/statusmoodcomments/{personId}/@self
For posting an additional parameter is needed to identify the individual status to comment against
* http://opensocial.myspace.com/roa/09/statusmoodcomments/{personId}/@self?postedDate={postedDate}

==={personId}===
This can be one of the following values:
* @me: Refers to the current user. @me can only be passed in when using the xoauth_requestor_id query string parameter or when passing in an OAuth token.
* An integer value: MySpace IDs are integers. For example, Tom is 6221. 6221 is a valid integer value.
* myspace.com.person.[integer value]: PersonIDs also support type identifier prepended to the integer value. Tom's value is myspace.com.person.6221.

==={postedDate}===
Part of the POST only. This is a required parameter for determining which status/mood to post a comment against:
The parameter can be in a number of different date format such as
* 10/21/2009 5:00 PM
* June 15, 2009 1:45 PM
* 2009-06-15T13:45:30.0900000
* Mon, 15 Jun 2009 20:45:30 GMT

==Testing==
===Positive===

====Test - Retrieve all comments for a given user====
http://opensocial.myspace.com/roa/09/statusmoodcomments/{personId}/@self
* Test - {personId} : @me ('''xoauth_requestor_id''' or '''oauth_token''' present in query string)
* Test - {personId} : integer value
* Test - {personId} : myspace.com.person.[integer value]

====Test - User commenting on their own status/mood====

http://opensocial.myspace.com/roa/09/statusmoodcomments/{personId}/@self?postedDate={postedDate}&format=json|xml

'''personId''' and '''postedDate''' are required; '''format''' defaults to 'json' if not specified

Setup:
# Login and update status/mood
# Find updated status/mood by retrieving the newly updated status/mood
# Add comment to status/mood update by using the key fields 'personId' and 'postedDate'
# The '''id''' in the POST body will be the same as '''personId''' in the query string
* Test - valid '''personId''', '''postedDate''', '''format''' not specified
{| border=1
|- bgcolor=#FF69B4
! Field ID !! Field Value
|-
| personId || @me | integer | myspace.com.person.[integer value]
|-
| postedDate || valid date/time value
|-
| POST data || <source lang="javascript">
{
"author":{"id":"56047906"},
"body":"this is a comment about your status",
}
</source>
|}

* Test - valid '''personId''', '''postedDate''', '''format=json'''
{| border=1
|- bgcolor=#FF69B4
! Field ID !! Field Value
|-
| personId || @me | integer | myspace.com.person.[integer value]
|-
| postedDate || valid date/time value
|-
| POST data || <source lang="javascript">
{
"author":{"id":"56047906"},
"body":"this is a comment about your status",
}
</source>
|}

* Test - valid '''personId''', '''postedDate''', '''format=xml'''
{| border=1
|- bgcolor=#FF69B4
! Field ID !! Field Value
|-
| personId || @me | integer | myspace.com.person.[integer value]
|-
| postedDate || valid date/time value
|-
| POST data || <source lang="XML">
<comment>
<author><id>56047906</id></author>
<body>this is a comment about your status</body>
</comment>
</source>
|}

====Test - User commenting another users' status/mood====
Setup:
# Make sure that you have the permission to add comments to status/mood by being a friend of the user
# Find status/mood by retrieving status/mood
# The '''id''' in the POST body is the posting user's id while the '''personId''' in the query string is the id of the status/mood user that is being commented against
# Add comment to status/mood update by using the key fields 'personId' and 'postedDate'
* Test - valid '''personId''', '''postedDate''', '''format''' not specified [Reference the examples for 'User commenting on their own status/mood']
* Test - valid '''personId''', '''postedDate''', '''format=json''' [Reference the examples for 'User commenting on their own status/mood']
* Test - valid '''personId''', '''postedDate''', '''format=xml''' [Reference the examples for 'User commenting on their own status/mood']

===Negative===
====Test - Retrieve all comments for a given user====
* Test - '''personId''': valid id that does not exist
* Test - '''personId''': invalid @mee
* Test - '''personId''': invalid integer value
* Test - '''personId''': valid myspace.com.person.[integer] that does not exist
* Test - '''personId''': invalid myspace.com.person.[bad value]
* Test - '''personId''': empty string

====Test - User commenting on their own status/mood====
=====Invalid query scenarios=====
* Test - no '''personId''' specified
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| [empty string] || valid value || not specified || valid value
|}

* Test - no '''postedDate''' specified
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || [empty string] || not specified || valid value
|}

* Test - no POST data specified
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || not specified || [empty string]
|}

* Test - '''format=json''', no POST data
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || json || [empty string]
|}

* Test - '''format=xml''', no POST data
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || xml || [empty string]
|}

* Test - '''format=xml''', POST data json
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || json || xml value
|}

* Test - '''format=json''', POST data xml
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || xml || json value
|}

=====POST data scenarios=====
* Test - invalid POST data specified
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || not specified || invalid json
|}

* Test - invalid POST data specified
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || not specified || valid json - bad author.id
|}

* Test - invalid POST data specified
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || not specified || valid json - bad body (characters that are not allowed)
|}

* Test - invalid POST data specified
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || not specified || invalid json
|}

* Test - invalid POST data specified
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || not specified || valid json - invalid fields
|}

* Test - '''format=xml''', invalid POST data
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || json || malformed xml
|}

* Test - '''format=xml''', invalid POST data
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || xml || valid xml - invalid fields
|}

* Test - '''format=xml''', invalid POST data
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || xml || valid xml - invalid comment.author.id
|}

* Test - '''format=xml''', invalid POST data
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || xml || valid xml - invalid comment.body (characters that are not allowed)
|}

* Test - invalid '''personId''' specified
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| invalid value || valid value || not specified || valid value
|}

* Test - invalid '''postedDate''' specified
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || invalid value || not specified || valid value
|}

* Test - invalid '''format''' specified
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || invalid format || valid value
|}

* Test - comment poster does not have permission
{| border=1
|- bgcolor=#FF69B4
! personId !! postedDate !! format !! POST data
|-
| valid value || valid value || not specified || valid value - author.id does not have permission
|}

====Test - User commenting another users' status/mood====

==Notes==
* The following are the fields of the statusmoodComments object.
** Collection of comment objects
** personId
** postedDate
** isFiltered
** isSorted
** isUpdatedSince
** itemsPerPage
** startIndex
** totalResults
* The following are the fields of the comment object. The fields marked in '''bold''' are default fields and will always be returned. Remaining fields will be returned whenever available.
** '''author'''
** '''commentId'''
** '''body'''
** '''postedDate'''
** culture
* author is an OpenSocial 0.9 Person type object. The following fields are supported; those marked in '''bold''' are default fields and will always be returned.
** '''id'''
** displayName
** profileUrl
** thumbnailUrl
* To request the comments of a StatusMood update, use the posted date of that individual update (this is a “posteddate” field for StatusMood updates) and pass it as the following parameter on the query string: posteddate=<date>. '''Please note posteddate is a must for this call.'''
* By default, the id of the comment author will be added to the result set, add the query parameter fields=author to get more information on the author.
* If the comment author is blocking the app, it will set displayName field of the author as "Private User" along with a null id.
* The maximum number of statusmood comments that an app can request is 100 (count=100).
* IF the app is blocked, it does not need any special permission to make a call to this API.

==Notes on POST==
* The following are the required fields of the comment object. The body is the comment to be posted against the status/mood.
** '''author'''
** '''body'''
* author is an OpenSocial 0.9 Person type object. The id field is required to determining who the author of this comment is.
** '''id'''
* You must pass in the postedDate as querystring to the endpoint as this is required to determine which status/mood you want to leave a comment for.
* You must be given permission to add comments to a status/mood by being a friend of the user or yourself can post a comment about your status/mood.
* To comment on user's status and mood, app needs following permission from the statusmood owner.

{| border="1" cellpadding="2" cellspacing="0"
|Permission
|Permission on App Settings page
|Notes
|-
| Viewer_update_mood_status
| Update Status and mood
| It will grant access to update user’s status-mood and comments.
|-
|}

Note – the app can only request permission for the viewer.

* Comment owner needs to be friend with status mood owner in order to comment on the status.

==Sample POST message==
*url : http://opensocial.myspace.com/roa/09/statusmoodcomments/6221/@self?postedDate=10/29/2009&format=json
*post body :
<pre>
{
"author":
{
"id":"56047906"
},
"body":"this is a comment about your status",
}
</pre>

*url : http://opensocial.myspace.com/roa/09/statusmoodcomments/6221/@self?postedDate=10/29/2009&format=xml
*post body :
<pre>
<comment>
<author>
<id>56047906</id>
</author>
<body>this is a comment about your status</body>
</comment>
</pre>

Stream Subscription API

2009-11-20T03:45:47Z

New page: Category:Early Adopters {| border="0" cellspacing="0" cellpadding="0" align="right" |- | | Back to MySpace REST Resources page. |} ==Base URI== The base uri for Stream Subscrip...

New page

[[Category:Early Adopters]]
{| border="0" cellspacing="0" cellpadding="0" align="right"
|-
|
| Back to [[MySpace REST Resources]] page.
|}

==Base URI==
The base uri for Stream Subscriptions on MySpace is
<source lang="text">
http://api.myspace.com/stream/subscription
</source>

==Description==

Developers will be able to receive user events (including activities, status updates, profile comments, etc) at an end point of their choosing. This data will be optionally qualified by various parameters such as event type or user type or the contents of a status update.

To receive this stream a developer needs to create a subscription that will describe the type of data the developer is interested in. There are 4 basic subscription types, and further filtering criteria that can be specified. You can receive updates for All users, users who have the developer's application installed, users who have the application installed and their friends, or a specific list of users.

This API allows you to:
* Create subscriptions to activities of MySpace users
* Modify your subscriptions
* View (GET) one or all of your subscriptions
* Delete one of all of your subscriptions

You will specify an HTTP endpoint, which will be called by MySpace with the activity data.

Activity information is detailed here: [[Standards_for_Activity_Streams | Standards for Activity Streams]]

==Supported HTTP Protocols==
* GET
* POST
* PUT
* DELETE
==Supported Input and Response Types==
* XML
* JSON

==Makeup of a Subscription==

* [[Stream_Subscription_Spec | Stream Subscription Spec]]
* [[Roa_09_stream_subscription_sample_json | JSON Example]]
* [[Roa_09_stream_subscription_sample_xml | XML Example]]

==URI Parameters==
The URI accepts parameters as part of the URI. URIs are of the following forms.

===stream/subscription===
This URI supports creating a subscription

Submit a subscription by POSTing a Stream Subscription in JSON or XML, in the format of the above samples.

The following are samples that should be send in the post body to create a subscription

===stream/subscription/{subscriptionId}===
*This URI supports updating, viewing, and deleting a subscription
*The samples below (same as the above endpoint) should be submitted in the body for a PUT for updates, or will be returned to a GET request.
*The subscription will be returned in JSON or XML, in the format of the above samples.

===stream/subscription/@all===
* This URI supports viewing and deleting all subscriptions
* The subscription will be returned in JSON or XML, in the format of the above samples, wrapped inside a "Subscriptions" outer element.

{{cURL|http://api.myspace.com/stream/subscription/@all}}

===Parameter Definitions===

===={subscriptionId}====
* An integer value: This will be returned as part of the URI when a subscription is first created. For example, http://api.myspace.com/stream/subscription/12345. It must be used to update, delete, or get a subscription.

==Optional Parameter==
====format====
Legal values: XML, JSON

JSON is the default format.
Use this parameter to specify XML.

=== Authentication ===

Outgoing requests to the subscriber will be signed using per the OAuth 1.0a spec. A hash of the body of the request will be included in the signature. An access token is not required.

Stream Subscription Query Spec

2009-11-20T03:36:25Z

←Older revision		Revision as of 03:36, 20 November 2009
Line 1:		Line 1:
		+
		+	[[Category:Early_Adopters]]
	=== Query Syntax ===		=== Query Syntax ===

Roa 09 stream subscription sample xml

2009-11-20T03:34:08Z

New page: ===NOTE: pass format=XML in the query string or JSON will be expected=== <source lang="xml"> <?xml version="1.0" encoding="utf-8"?> <Subscription id="4532342"> <Type>ApplicationUsers</...

New page

===NOTE: pass format=XML in the query string or JSON will be expected===

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<Subscription id="4532342">
<Type>ApplicationUsers</Type>
<Endpoint><![CDATA[http://api.abetterspamservice.ru/getmyspacedata.php]]></Endpoint>
<Query>
<Or>
<And>
<Object>Audio</Object>
<Verb>Play</Verb>
<UserType>Band</UserType>
</And>
<And>
<EventSource>ApplicationId.123456</EventSource>
<Or>
<Location Lat="36.1" Lon="-115.1" Radius="30" />
<Location Lat="28.7" Lon="-95.3" Radius="1000" />
</Or>
<Not>
<Text><![CDATA[Michael Jackson]]></Text>
</Not>
</And>
</Or>
</Query>
<MetaData>UserInfo,UserSubscribers,ApplicationData</MetaData>
<BatchSize>1000</BatchSize>
<Rate>100</Rate>
<Format><![CDATA[application/atom+xml]]></Format>
<UserList>
<AddList>6221,452341,4322</AddList>
<RemoveList>63453,142311,896784</RemoveList> 
</UserList>
</Subscription>
</source>

Roa 09 stream subscription sample json

2009-11-20T03:33:46Z

New page: <source lang="javascript"> {"Subscription" : { "id" : 4532342, "Type" : "ApplicationUsers", "Endpoint" : "http://api.abetterspamservice.ru/getmyspacedata.php", "Query" : {"Or" : [ ...

New page

<source lang="javascript">
{"Subscription" : {
"id" : 4532342,
"Type" : "ApplicationUsers",
"Endpoint" : "http://api.abetterspamservice.ru/getmyspacedata.php",
"Query" :
{"Or" : [
{"And" : [
{"Object" : "Audio"},
{"Verb" : "Play"},
{"UserType" : "Band"}
]},
{"And" : [
{"EventSource" : "ApplicationId.123456"},
{"Or" : [
{"Location" : {"Lat" : 36.1, "Lon" : -115.1, "Radius" : 30}},
{"Location" : {"Lat" : 28.7, "Lon" : -95.3, "Radius" : 1000}}
]},
{"Not" : [
{"Text" : "Michael Jackson"}
]}
]}
]},
"MetaData" : "UserInfo,UserSubscribers,ApplicationData",
"BatchSize" : 1000,
"Rate" : 100,
"Format" : "application/atom+xml",
"UserList" : {
"AddList" : [6221,452341,4322],
"RemoveList" : [63453,142311,896784]
}
}}
</source>

Stream Subscription Query Spec

2009-11-20T03:33:17Z

New page: === Query Syntax === Supported Operators: *AND *OR *NOT A query consists of query elements, which can be combined using logical. Each element consists of an Element Type and a value va...

New page

=== Query Syntax ===

Supported Operators:
*AND
*OR
*NOT

A query consists of query elements, which can be combined using logical. Each element consists of an Element Type and a value valid for that type. To constrain on a User Type, the Element Type is UserType, and valid values are Regular, Band, Comedian, Filmmaker. The elements and logical operators can be expressed as either XML or JSON. A possible query element is then <UserType>Band</UserType>.

=== Query Examples ===

This query returns events of type Music or Video raised by Bands or Comedians, or, events from a specific application raised within 30 miles of Las Vegas, or 1000 miles of the Gulf of Mexico, that DO NOT contain the phrase “Michael Jackson”.

XML:

<source lang="xml">
<Or>
<And>
<EventType>Music</EventType>
<EventType>Video</EventType>
<UserType>Band</UserType>
<UserType>Comedian</UserType>
</And>
<And>
<EventSource>ApplicationId.123456</EventSource>
<Or>
<Location Lat="36.1" Lon="-115.1" Radius="30" />
<Location Lat="28.7" Lon="-95.3" Radius="1000" />
</Or>
<Not>
<Text><![CDATA[Michael Jackson]]></Text>
</Not>
</And>
</Or>
</source>

JSON:
<source lang="javascript">
{"Or" : [
{"And" : [
{"EventType" : "Music"},
{"EventType" : "Video"},
{"UserType" : "Band"},
{"UserType" : "Comedian"}
]},
{"And" : [
{"EventSource" : "ApplicationId.123456"},
{"Or" : [
{"Location" : {"Lat" : 36.1, "Lon" : -115.1, "Radius" : 30}},
{"Location" : {"Lat" : 28.7, "Lon" : -95.3, "Radius" : 1000}}
]},
{"Not" : [
{"Text" : "Michael Jackson"}
]}
]}
]}
</source>

Stream Subscription Spec

2009-11-20T03:32:26Z

New page: Category:Early_Adopters Also see: Stream Subscription Query Spec for details on the Query portion ====Samples==== * [[Roa_09_stream_subscription_s...

New page

[[Category:Early_Adopters]]
Also see: [[Stream_Subscription_Query_Spec | Stream Subscription Query Spec]] for details on the Query portion

====Samples====
* [[Roa_09_stream_subscription_sample_json | JSON Example]]
* [[Roa_09_stream_subscription_sample_xml | XML Example]]

=== Subscription Components ===

*Type
**"All" - All Events
**"ApplicationUsers" - Events from application users
**"ApplicationUsersAndFriends" - Events from application users and friends of application users
**"UserList" - Specific users
*Endpoint
**A URL to which events will be sent
*[[Stream_Subscription_Query_Spec | Query]] - Events can be filtered by the criteria below using a simple language
**Event Activity Type
***Music, Video, Photo [TODO: Enumerate all supported types ]
**Event Activity Source
***Values: "twitter", "mobile", "applicationId.123456"
**User Type
***Regular, Band, Comedian, Filmmaker, Advertiser, Celebrity
**Location
***Latitude
***Longitude
***Radius - Integer, Miles
**Text
***A word or a phrase within the event. Alphanumerics only, up to 140 characters
**Culture
***5 character culture code
*Batch Size
**Optional, 1 by default
**An integer from 1 to 10000
*Rate
**Percent of matching events to send to subscriber
**An integer from 1 to 100
*Format
**Values: "application/atom+xml", "application/json "
*Meta Data
**Comma delimited list of meta data types to include. Possible values:
**"UserInfo"
***UserId , DisplayName, LargeProfileImage, MediumProfileImage, UserType, Nickname, ProfileUrl, HasApp
**"UserSubscribers" - User’s subscribers (followers)
***Up to 1000 IDs only
**"ApplicationData" - User’s application data
*Add User List / Remove User List
**Optional. Comma delimited integers.

Category:Early Adopters

2009-11-20T03:23:33Z

New page: Welcome!

New page

Welcome!

Category:Early

2009-11-20T03:22:52Z

New page: Welcome

New page

Welcome

Template:CURL

2009-11-20T03:12:39Z

New page: [http://developer.myspace.com/OAuthTool.mvc?url={{{1}}} cURL it]

New page

[http://developer.myspace.com/OAuthTool.mvc?url={{{1}}} cURL it]

Portable Contacts REST Resources

2009-11-19T22:47:34Z

The fields Parameter:

←Older revision		Revision as of 22:47, 19 November 2009
Line 497:		Line 497:
	<td>		<td>
	<p>added new photos":[{"value": <br>"http:\/\/a229.ac-images.my<br>spacecdn.c om\/ima<br>ges01\/118 \/s_3dcfafe8145a40fc46<br>edacfebe7eaa94.jpg",<br>"type":"thumnbnail"}, {"value":"http:\/\/a229.acimages.<br>myspacecdn.com\/images01 \/118\/m_3dcfafe8145a40<br>fc46edacfebe7eaa94.jpg",<br>"type": "medium"},<br>{"value":"http:\/\/a229.ac-im<br>ages. myspacecdn.com \/images01\/118\/l_<br>3dcfafe8145a40fc46eda<br>cfebe7eaa94.jpg", <br>"type":"large"}]}]</p></td>		<p>added new photos":[{"value": <br>"http:\/\/a229.ac-images.my<br>spacecdn.c om\/ima<br>ges01\/118 \/s_3dcfafe8145a40fc46<br>edacfebe7eaa94.jpg",<br>"type":"thumnbnail"}, {"value":"http:\/\/a229.acimages.<br>myspacecdn.com\/images01 \/118\/m_3dcfafe8145a40<br>fc46edacfebe7eaa94.jpg",<br>"type": "medium"},<br>{"value":"http:\/\/a229.ac-im<br>ages. myspacecdn.com \/images01\/118\/l_<br>3dcfafe8145a40fc46eda<br>cfebe7eaa94.jpg", <br>"type":"large"}]}]</p></td>
-	<td align="middle">~~YES~~</td>	+	<td align="middle">NO</td>
	<td align="middle">YES</td></tr></table>		<td align="middle">YES</td></tr></table>

OpenSocial v0.9 Activities

2009-11-18T01:11:49Z

←Older revision		Revision as of 01:11, 18 November 2009
Line 108:		Line 108:

	==Activity Streams Extensions==		==Activity Streams Extensions==
-	The MySpace OpenSocial 0.9 activities endpoints have recently added BETA support for Activity Streams objects represented in JSON and plain old XML~~. These properties are experimental and subject to change~~. Find more information about Activity Streams on the [http://activitystrea.ms/ web site].	+	The MySpace OpenSocial 0.9 activities endpoints have recently added BETA support for Activity Streams objects represented in JSON and plain old XML. Find more information about Activity Streams on the [http://activitystrea.ms/ web site].

	*actor: Describes the person who performed the activity.		*actor: Describes the person who performed the activity.

OpenSocial 0.9 MediaItems

2009-11-18T00:57:27Z

←Older revision		Revision as of 00:57, 18 November 2009
(One intermediate revision not shown.)
Line 47:		Line 47:
	**location		**location
	**lastUpdated		**lastUpdated
-	**msTaggedPeople
	**startTime		**startTime
	**taggedPeople		**taggedPeople
Line 84:		Line 83:
	**thumbnailUrl		**thumbnailUrl
	**url		**url
-
-	*msTaggedPeople is a collection of OpenSocial 0.9 Person objects. The following fields are always returned.
-	**id
-	**displayname
-	**profileUrl
-	**thumbnailUrl
-	**x1 (upper-left x-coordinate of the tag rectangle)
-	**y1 (upper-left y-coordinate of the tag rectangle)
-	**x2 (bottom-right x-coordinate of the tag rectangle)
-	**y2 (bottom-right y-coordinate of the tag rectangle)

	*The following are MySpace extended fields		*The following are MySpace extended fields
Line 141:		Line 130:

	*Only the title and description of a video can be updated. They cannot be null or empty. If a null is passed it will assume the previous value.		*Only the title and description of a video can be updated. They cannot be null or empty. If a null is passed it will assume the previous value.
-
-	*The fields taggedPeople and msTaggedPeople are not supported by APIs that return image collections. You can ask for the msNumTags field in your request, this will tell you which imageIds have tags. If you want to fetch the actual tag information for one of the images make a call to that particular mediaItem URI (for example, mediaItems/<albumId>/<imageId>). Pass the query parameters fields=taggedPeople or fields=msTaggedPeople to retrieve the tag information. [NOTE - as per the OpenSocial spec, taggedPeople only returns the list of userIds. msTaggedPeople returns some basic user information for valid MySpace users. Non-MySpace users tagged in the image will have the displayName field populated.]

	* Mobile URLs in MediaItem objects can be returned by appending wap=1 to the query-string.		* Mobile URLs in MediaItem objects can be returned by appending wap=1 to the query-string.

OpenSocial v0.9 Notifications

2009-11-18T00:52:13Z

←Older revision		Revision as of 00:52, 18 November 2009
Line 1:		Line 1:
-	~~[[Category:OpenSocial_v0.9_REST_Resources]]~~
	==Base URI==		==Base URI==
	The base uri for notifications on MySpace is http://opensocial.myspace.com/roa/09/notifications. This endpoint only supports POST and PUTs at this time.		The base uri for notifications on MySpace is http://opensocial.myspace.com/roa/09/notifications. This endpoint only supports POST and PUTs at this time.

OpenSocial v0.9 Groups

2009-11-18T00:51:58Z

←Older revision		Revision as of 00:51, 18 November 2009
Line 1:		Line 1:
-	~~[[Category:OpenSocial_v0.9_REST_Resources]]~~
	==Base URI==		==Base URI==
	The base uri for Activities on MySpace is http://opensocial.myspace.com/roa/09/groups. This endpoint supports GETs, PUTs, and POSTs.		The base uri for Activities on MySpace is http://opensocial.myspace.com/roa/09/groups. This endpoint supports GETs, PUTs, and POSTs.

OpenSocial v0.9 AppData

2009-11-18T00:51:47Z

←Older revision		Revision as of 00:51, 18 November 2009
Line 1:		Line 1:
-	~~[[Category:OpenSocial_v0.9_REST_Resources]]~~
	==Base URI==		==Base URI==
	The base uri for AppData on MySpace is http://opensocial.myspace.com/roa/09/appdata. This endpoint supports GETs, PUTs, POSTs, and DELETEs.		The base uri for AppData on MySpace is http://opensocial.myspace.com/roa/09/appdata. This endpoint supports GETs, PUTs, POSTs, and DELETEs.

OpenSocial v0.9 Albums

2009-11-18T00:51:32Z

←Older revision		Revision as of 00:51, 18 November 2009
Line 1:		Line 1:
-	~~[[Category:OpenSocial_v0.9_REST_Resources]]~~
-
	==Base URI==		==Base URI==
	The base uri for Albums on MySpace is http://opensocial.myspace.com/roa/09/albums. This endpoint supports GETs, PUTs, and POSTs.		The base uri for Albums on MySpace is http://opensocial.myspace.com/roa/09/albums. This endpoint supports GETs, PUTs, and POSTs.

OpenSocial v0.9 Activities

2009-11-18T00:51:20Z

(Difference between revisions)

OpenSocial v0.9 StatusMood

2009-11-17T21:19:35Z

←Older revision		Revision as of 21:19, 17 November 2009
Line 37:		Line 37:
	** recentComments		** recentComments
	** '''status'''		** '''status'''
		+	** source
	** '''userId'''		** '''userId'''
	* author is a type of Person OpenSocial 0.9 object. The following fields are supported. ('''bold''' are default fields and always be returned)		* author is a type of Person OpenSocial 0.9 object. The following fields are supported. ('''bold''' are default fields and always be returned)
Line 49:		Line 50:
	** '''postedDate'''		** '''postedDate'''
	** culture		** culture
		+	* source is a type of source object. The following fields are supported.
		+	**externalId
		+	**appId
		+	**name
		+	**url
		+	**imageUrl
	* The following are the fields of the StatusMoodList object		* The following are the fields of the StatusMoodList object
	** Collection of StatusMood objects		** Collection of StatusMood objects
Line 64:		Line 71:
	* To retrieve status-mood of perticular user's custom friends category, use "/@friends" API calls and pass following query parameters: filterby=@group&filterop=equals&filtervalue=<custom grpId>		* To retrieve status-mood of perticular user's custom friends category, use "/@friends" API calls and pass following query parameters: filterby=@group&filterop=equals&filtervalue=<custom grpId>
	* To retrieve culture specific moodlist to moods API, pass queryparameter culture=<culture value>, for an example culture="en-US" or culture="en"		* To retrieve culture specific moodlist to moods API, pass queryparameter culture=<culture value>, for an example culture="en-US" or culture="en"
		+	* Now MySpace allows to sync/update statusmood from various sources like twitter, you can get that information by passing query parameter fields=source to your requests.
		+
	* Facts about the FETCH StatusMood endpoint:		* Facts about the FETCH StatusMood endpoint:
	** By default, the id of the StatusMood and comment author will be added to the result set, add the query parameter fields=author to get more information on the author.		** By default, the id of the StatusMood and comment author will be added to the result set, add the query parameter fields=author to get more information on the author.
Line 82:		Line 91:
	*** MySpace allows only certain images for the mood image. Use @supportedmood call to get a list of MySpace supported mood details.		*** MySpace allows only certain images for the mood image. Use @supportedmood call to get a list of MySpace supported mood details.
	*** You may optionally pass a geo-location (latitude and longitude) on the currentLocation property.		*** You may optionally pass a geo-location (latitude and longitude) on the currentLocation property.
-	* Please notice it's '''''S'''''tatusMood and '''''S'''''tatusMoodList~~, with the "S" capitalized~~.	+	* Please notice it's '''''S'''''tatusMood and '''''S'''''tatusMoodList.
	* To make a call to the @supportedmood endpoint, the app needs to be installed.		* To make a call to the @supportedmood endpoint, the app needs to be installed.
-	* ~~To call the fetch/update~~ StatusMood APIs~~, the app needs to be installed and also it needs the following permissions:~~	+	* '''Permissions to access StatusMood APIs''' -
-		+	** The app can make a request @self calls if app is not blocked and user has not opt-out from sharing basic data to non installed apps.
-	~~{\| border="1" cellpadding="2" cellspacing="0"~~	+	** The app needs to be installed to make any non-@self API calls and to update the user status mood.
-	~~\|Permission~~	+
-	~~\|Permission on App Settings page~~	+
-	~~\|Notes~~	+
-	\|-	+
-	~~\| Viewer_contact_info~~	+
-	~~\| View my personal info & details~~	+
-	~~\| It will grant access to view user’s mood~~ and ~~status.~~	+
-	\|-	+
-	~~\| Viewer_update_mood_status~~	+
-	~~\| Currently it’s not available on UI~~	+
-	~~\| It will grant access~~ to ~~update user’s mood and status~~.	+
-	\|-	+
-	~~\| Viewer_access_to_friends_list~~	+
-	~~\| App gets this permission automatically if~~ app is installed	+
-	~~\| This permission gives access~~ to ~~person’s friends’ data.~~	+
-	\|-	+
-	\|}	+
-		+
-	~~Note –~~ the ~~app can only request permission for the viewer~~.	+

	==Supported URIs and Filters by StatusMood endpoints==		==Supported URIs and Filters by StatusMood endpoints==
Line 3,073:		Line 3,063:

	=== Update StatusMood ===		=== Update StatusMood ===
-	'''Request''': PUT http://opensocial.myspace.com/roa/09/statusmood/@me/@self	+	'''Request in JSON''': PUT http://opensocial.myspace.com/roa/09/statusmood/@me/@self
		+	<source lang="javascript">
		+	{
		+	"currentLocation":{
		+	"latitude":"47.604832",
		+	"longitude":"-122.337549"
		+	},
		+	"moodName":"excited",
		+	"status":"Working on PHP SDK"
		+	}
		+	</source>

	'''Response''':		'''Response''':
		+	<source lang="javascript">
		+	{
		+	"statusLink":"http:\/\/opensocial.myspace.com\/roa\/09\/statusmood\/myspace.com.person.478501013\/@self"
		+	}
		+	</source>
		+
		+	'''Request in XML''': PUT http://opensocial.myspace.com/roa/09/statusmood/@me/@self?format=xml
		+	<source lang="xml">
		+	<StatusMood xmlns="http://ns.myspace.com/2009/statusmood" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
		+	<currentLocation xmlns:a="http://ns.opensocial.org/2008/opensocial">
		+	<a:latitude>47.618688</a:latitude>
		+	<a:longitude>-122.343091</a:longitude>
		+	</currentLocation>
		+	<moodName>excited</moodName>
		+	<status>Working on PHP SDK</status>
		+	</StatusMood>
		+	</source>
		+
		+	'''Response''':
		+	<source lang="xml">
		+	<Result xmlns="http://ns.opensocial.org/2008/opensocial" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
		+	<statusLink>http://opensocial.myspace.com/roa/09/statusmood/myspace.com.person.478501013/@self</statusLink>
		+	</Result>
		+	</source>

	==== PHP Sample====		==== PHP Sample====

OpenSocial 0.9 MediaItems

2009-11-17T21:07:14Z

(Difference between revisions)

OpenSocial v0.9 MediaItemComments

2009-11-17T21:05:53Z

New page: ==Base URI== The base URI for mediaItemComments on MySpace is http://opensocial.myspace.com/roa/09/mediaitemcomments. This endpoint currently supports only GET. ==URI Parameters== Paramet...

New page

==Base URI==
The base URI for mediaItemComments on MySpace is http://opensocial.myspace.com/roa/09/mediaitemcomments. This endpoint currently supports only GET.

==URI Parameters==
Parameters are accepted as part of the URI. URIs are of the following forms:
This url as a GET will return all the comments.
* http://opensocial.myspace.com/roa/09/mediaitemcomments/{personId}/@self/{albumId}/{mediaItemId}

==={personId}===
This can be one of the following values:
* @me: Refers to the current user. @me can only be passed in when using the xoauth_requestor_id query string parameter or when passing in an OAuth token.
* An integer value: MySpace IDs are integers. For example, Tom is 6221. 6221 is a valid integer value.
* myspace.com.person.[integer value]: PersonIDs also support type identifier prepended to the integer value. Tom's value is myspace.com.person.6221.

==={albumId}===

The albumId indicates which group of media items from a single album from the group identified by {selector} should be returned. This is used when an application wants to display the contents of a single album. Valid values are -
* An integer value: Gives the integer identifier of the album.
* myspace.com.album.[integer value]
* @videos if the media items are videos. On MySpace, videos do not belong to specific albums.

==={mediaItemId}===

The mediaItemId indicates which single media item from the album identified by {albumId} should be returned. This is used when an application wants to display a single mediaItem. Valid values are -
* An integer value: Gives the integer identifier of the mediaItem.
* myspace.com.mediaItem.image.[integer value] for image
* myspace.com.mediaItem.video.[integer value] for video

==Notes==
* The following are the fields of the mediaItemComments object.
** Collection of comment objects
** personId
** id
** isFiltered
** isSorted
** isUpdatedSince
** itemsPerPage
** startIndex
** totalResults
* The following are the fields of the comment object. The fields marked in '''bold''' are default fields and will always be returned. Remaining fields will be returned whenever available.
** '''author'''
** '''commentId'''
** '''body'''
** '''postedDate'''
** culture
* author is an OpenSocial 0.9 Person type object. The following fields are supported; those marked in '''bold''' are default fields and will always be returned.
** '''id'''
** displayName
** profileUrl
** thumbnailUrl
* By default, the id of the comment author will be added to the result set, add the query parameter fields=author to get more information on the author.
* If the comment author is blocking the app, it will set displayName field of the author as "Private User" along with a null id.
* The maximum number of mediaItem comments that an app can request is 100 (count=100).
* To fetch comments of a mediaItem, app needs same permission as it requires to fetch metadata of that mediaItem. Please see [[OpenSocial0.9MediaItems#Notes|MediaItems permission model]]

Category:OpenSocial v0.9 REST Resources

2009-11-17T21:05:25Z

Data Representations:

←Older revision		Revision as of 21:05, 17 November 2009
Line 57:		Line 57:

	'''Detail:''' [[OpenSocial 0.9 MediaItems]]		'''Detail:''' [[OpenSocial 0.9 MediaItems]]
		+
		+	===MediaItemComments===
		+
		+	'''Resource:''' <pre>http://opensocial.myspace.com/roa/09/mediaitemcomments</pre>
		+
		+	'''Description:''' On MySpace, users can leave a custom comment on uploaded images, this API provides support for those types of comments.
		+
		+	'''Detail:''' [[OpenSocial v0.9 MediaItemComments]]

	===Activities===		===Activities===

OpenSocial v0.9 ProfileComments

2009-11-17T21:01:32Z

←Older revision		Revision as of 21:01, 17 November 2009
Line 36:		Line 36:
	* If the comment author is blocking the app, it will set displayName field of the author as "Private User" along with a null id.		* If the comment author is blocking the app, it will set displayName field of the author as "Private User" along with a null id.
	* The maximum number of profile comments that an app can request is 100 (count=100).		* The maximum number of profile comments that an app can request is 100 (count=100).
-	* To fetch data from this API, the app needs to be installed ~~and have the following permissions:~~	+	* '''To fetch data from this API, the app needs to be installed.'''
-		+
-	~~{\| border="1" cellpadding="2" cellspacing="0"~~	+
-	~~\|Permission~~	+
-	~~\|Permission on App Settings page~~	+
-	~~\|Notes~~	+
-	\|-	+
-	~~\| Viewer_contact_info~~	+
-	~~\| View my personal info & details~~	+
-	~~\| It will grant access to view user’s profile comments.~~	+
-	\|-	+
-	\|}	+
-		+
-		+
-	~~Note – the app can only request permission for the viewer~~.	+

OpenSocial v0.9 StatusMoodComments

2009-11-17T20:59:38Z

←Older revision		Revision as of 20:59, 17 November 2009
Line 5:		Line 5:
	Parameters are accepted as part of the URI. URIs are of the following forms:		Parameters are accepted as part of the URI. URIs are of the following forms:
	* http://opensocial.myspace.com/roa/09/statusmoodcomments/{personId}/@self		* http://opensocial.myspace.com/roa/09/statusmoodcomments/{personId}/@self
		+	* http://opensocial.myspace.com/roa/09/statusmoodcomments/{personId}/@self?postedDate={postedDate}

	==={personId}===		==={personId}===
Line 38:		Line 39:
	* If the comment author is blocking the app, it will set displayName field of the author as "Private User" along with a null id.		* If the comment author is blocking the app, it will set displayName field of the author as "Private User" along with a null id.
	* The maximum number of statusmood comments that an app can request is 100 (count=100).		* The maximum number of statusmood comments that an app can request is 100 (count=100).
-	* ~~To fetch data from~~ this API~~, the~~ app ~~needs to be installed~~ and ~~have the following permissions:~~	+	* The app can make a request to this API if app is not blocked and user has not opt-out from sharing basic data to non installed apps.
-		+
-	~~{\| border="1" cellpadding="2" cellspacing="0"~~	+
-	~~\|Permission~~	+
-	~~\|Permission on App Settings page~~	+
-	~~\|Notes~~	+
-	\|-	+
-	~~\| Viewer_contact_info~~	+
-	~~\| View my personal info & details~~	+
-	~~\| It will grant access~~ to ~~view user’s status mood comments.~~	+
-	\|-	+
-	\|}	+
-		+
-		+
-	~~Note – the app can only request permission for the viewer~~.	+

←Older revision		Revision as of 04:14, 20 November 2009
Line 35:		Line 35:
	* JSON		* JSON

-	~~==More Documents on Search==~~

-	* [[MySpace_Search_Spec_1.0 \| MySpace Search Spec 1.0]]
-	* [[MySpace_OpenSearch_Extension_1.0 \| MySpace OpenSearch Extension 1.0]]

	==Examples of Search==		==Examples of Search==