An OAuth token used by developers to gain access to the private data on behalf of the end user. An access token is used in place of other private credentials that the end user may want to keep private, such as a username and password.
See Consumer Key.
An Open App or and OAuth application.
A browser-based tool that allows developers to configure, preview, and publish Open Applications on the Yahoo! Application Platform.
An Application ID is a string that uniquely identifies your application. Think of it like a User-Agent string. The Application is assigned by the Yahoo! Application Platform when you register your application.
A URL where your Web-based application is located. You must provide the Application URL when you first apply for an Web-based OAuth Application in the My Projects page.
The full view of an Open Application. You can access the Canvas view through the My Projects page as well as through your application URL (apps.yahoo.com/-appID)
See Also Small view.
The visual container of an Open Application. End users manage Open Applications by selecting the menu items of the Chrome.
Within Social Platform, a connection is a reciprocal 2-way connection between 2 users. Connections are the people that matter most to a user.
In OAuth, the Consumer stands for the developer, the developer's application, or the developer's Web site that uses OAuth to access private data from Yahoo!.
An OAuth-related key used by a developer to identify itself to Yahoo!. Also known in Yahoo! as the API Key.
A secret used by a developer to prove ownership of the Consumer Key. Also known in Yahoo! as the Shared Secret.
A record that a user stores about another user, without requiring any permission. A users address book contains the same relationships as do Contacts.
The Contact API provides the URIs with which you can access the entries under a person's Address Book Contacts.
A setting of an Open Application that allows developers to specify a small icon that represents their applications as part of the Yahoo! Updates service.
A method of limiting the number of results returned from an API request. Filters can be used in the Yahoo! Social Platform to retrieve part of a collection resource.
The area on a web page where the end user can search, browse, and install Open Applications.
A GUID is a unique 26-byte-long string that identifies a person associated with the data of the resource. The GUID is used within Yahoo! instead of a Yahoo! ID because it is permanent and is not attached to any private information such as an email address.
The GUID of the user currently running the application. Available through the Social Directory API.
A Open Application feature that sends email invitations to a user's connections in order to create a mutually confirmed relationship.
The physical page, represented by a static URL, where an Open Application's Canvas view appears. Chrome is visible on the Landing Page.
A part of the Paging, matrix parameters let the application retrieve part of a collection when calling an HTTP GET operation.
An aggregated list of a user's Open Applications. When a user installs an Open is appears in My Applications regardless of where the installation takes place.
A dashboard on YDN that enables you to manage and register Open Applications and OAuth Applications. You can also register apps using the older BBAuth standard.
A Open Application feature that enables a user to send a notification through email to other end users.
OAuth is an open standard that allows Yahoo! users to share their private resources stored on Yahoo! with developers without having to hand out their username and password.
A web application that works on the Yahoo! Application Platform. Open Applications allow third-party content to plug into Yahoo! using a Canvas view and a Small view.
A set of open-standard APIs created for social apps. An application based on OpenSocial APIs can be used with any social network that supports them.
A method of limiting the number of results returned from an API request. In the Yahoo! Social Platform, paging is indicated with matrix parameters.
A profile is the personal identity of a user on Yahoo! Each user has a Profiles Page that he or she can customize to display different aspects of his or her profile data. Developers can also use the Social Directory APIs to access this profile data, provided the user authorizes that access.
A chunk of related information available through a particular URI (Uniform Resource Identifier).
REST stands for Representational State Transfer. Most Yahoo! Web services use "REST-Like" operations over HTTP requests with parameters URL-encoded into the request.
An OAuth token used by developers to obtain authorization from end-users. The Request Token is exchanged with Yahoo! for an Access Token.
A permission setting that specifies access to a Yahoo! user's non-public data. You must specify the Scopes needed by your applications register for an API key on the Yahoo! Developer Network (YDN).
In OAuth, the Service Provider is Yahoo!, the entity that provisions access to private data using OAuth.
See Consumer Secret.
An abbreviated or reduced version of an Open Application that runs embedded in a Yahoo! Web page.
See Also Canvas view.
The Social Directory API provides profile (identity) and connection (relationship) information about Yahoo! users.
An AI that allows developers to collect and disseminate the status of users, such as what they are doing or how they are feeling.
Data from the Social Directory that describes a person with only a subset of the information available in the user's profile. Requesting tinyusercard allows for quick cached calls to formatted profile data.
OAuth authorization between three parties: (1) the end user (User), (2) the application (the Consumer), and (3) the private data source (the Service Provider). An application that uses the Yahoo! Social Directroy APIs, for example, needs authorization by the end user to access private social data.
OAuth authorization between two parties: (1) an application (the Consumer) and (2) the public data source (the Service Provider). The public data source can be a Web service or Web feeds such as RSS or Atom feeds. A public data source does not require authorization from the end user of the application.
An API that allows developer applications to both generate and display activities and events that occur on and off Yahoo!. Updates is a feature that displays a stream of user events and activities. An user can view this on their Yahoo! Profile page.
Core data in the user's profile, containing slightly more information than the tinyusercard.
Settings for a specific module that the end user can specify. At runtime, the module code can access these settings through variables. User configurations are available to all views in a module.
A file you must create on your Web site when you register for an API Key on the YDN My Projects page. This file verifies that your domain is valid.
The rendering environment, APIs, and tools that enable developers to build Open Applications, which are available throughout Yahoo!.
Yahoo!'s developer site, providing access to Yahoo! Web services and APIs. Related documentation and support is also available.
Similar in format to HTML, Yahoo! Markup Language (YML) provides functionality to Open Applications in a safe and standardized fashion. Yahoo! processes the YML and converts it into HTML. YML allows features that allow developers to easily implement features, such as a friend selector or a message dialog.
A mediator service platform that enables developers to query, filter, and combine data across Yahoo! Web services. YQL has a syntax similar to SQL SELECT statements.
A suite of social APIs comprised of the Social Directory, Contacts, Status and Updates. This REST-based API enables you to create applications that access Yahoo! social data.