API Documentation

Current API Methods

• activities/group_timeline (v1) - Retrieve a listing of the activities equivalent to those shown on the group profile of the specified group. Returns a maximum of 10 activities.
• activities/home_timeline (v1) - Retrieve a listing of the activities equivalent to those shown on the homepage of the authenticating user. Returns a maximum of 15 activities.
• comments (v1) - Retrieve a listing of the comments on a particular auditable object
• comments/create (v1) - Add a comment to a particular auditable object
• events (v1) - Retrieve a listing of the events for a group
• events/update_score (v1) - Add a score to a game
• feedbacks/create (v1) - Send feedback about Weplay
• friendships/check (v1) - Check which of the specified user ids represent friends of the target member
• group (v1) - Retrieve information about a particular group
• group_members (v1) - Retrieve a listing of the members of a Weplay group the user is a member of. Notes: Weplay teams can consist of Weplay members as well as people who have not yet joined Weplay, which the API calls benchwarmers. Non-team groups only consist of Weplay members, and member information is less rich than in a team (i.e. no positions, jersey numbers, and the like).
• group_message (v1) - Get a group message
• group_messages (v1) - Get the group messages for a group
• group_messages/create (v1) - Post/send a message to the group
• group_replies (v1) - Get the group message replies for a group message
• group_replies/create (v1) - Post a reply to a group message
• groups (v1) - Retrieve a listing of the Weplay groups a user is a member of
• likes (v1) - Register that a user likes a particular auditable object
• location (v1) - Retrieve information about a particular location
• media (v1) - Get a reverse chronological listing of photos and videos
• media/create_from_upload (v1) - DEPRECATED - If you have an upload token from a call to media/new_upload_session and subsequent upload, you can then call this method to create an image or video on Weplay from the uploaded file.
• media/create_from_upload (v2) - If you have an upload token from a call to media/new_upload_session and subsequent upload, you can then call this method to create an image or video on Weplay from the uploaded file.
• media/new_upload_session (v1) - DEPRECATED - Use this method to get a valid session and URL to upload media. POST multipart form data to this URL with a field named fileData containing a media file to be uploaded. Use the upload_token_id that is returned to initiate a call to our media/create_from_upload endpoint
• media/new_upload_session (v2) - Use this method to get a valid session and URL to upload media. POST multipart form data to this URL with a field named fileData containing a media file to be uploaded. Use the upload_token_id that is returned to initiate a call to our media/create_from_upload endpoint
• networks/check (v1) - Check which of the specified user ids represent friends or teammates of the target member
• props (v1) - Retrieve a listing of the props received by a particular user
• props/available (v1) - Retrieve a listing of the props available to the authenticating for giving to another user
• props/create (v1) - Give a prop to another user
• sports (v1) - Retrieve sports
• statuses/update (v1) - Update the user's weplay status
• tweets/create (v1) - Publish a new tweet to subscribed fan pages (requires special application access)
• tweets/destroy (v1) - Delete an already-published tweet from subscribed pages (requires special application access)
• twitter_subscriptions (v1) - Retrieve a list of Twitter user ids corresponding to active page subscriptions (requires special application access)
• user (v1) - Retrieve information about a particular user
• user/friends_and_teammates (v1) - Retrieve a collection of the authenticated current user's friends and teammates
• webhooks (v1) - Retrieve a list of webhooks registered by your application on behalf of the authenticated user. For more information about webhooks, see http://wiki.webhooks.org/. Weplay currently supports webhooks for 'status_created' and sends data in JSON.
• webhooks/create (v1) - Register a webhook, on behalf of the authenticated user, to be POSTed to when a specific event occurs on Weplay. For more information about webhooks, see http://wiki.webhooks.org/. Weplay currently supports webhooks for 'status_created' and sends data in JSON.
• webhooks/destroy (v1) - Delete a previously registered webhook. For more information about webhooks, see http://wiki.webhooks.org/.

Authentication

Weplay currently supports two modes of authentication: OAuth and HTTP Basic Authentication.

OAuth is an authentication protocol that allows users to approve an application to act on their behalf without sharing their password. Once a user grants access to your application, your application uses an access token to perform API calls. For more information about the specifics of the OAuth, see oauth.net.

Register your application for free to receive OAuth access.

While using Oauth for your authentication scheme is strongly encouraged, for convenience and ease of development Weplay also provides access to its API by using HTTP Basic Authentication. This enables developers to explore the API with simple tools such as cURL. Because HTTP Basic Authentication requires transmission of the user's password, all API calls with HTTP Basic Authentication are required to use SSL.