A tag is a keyword or label that categorizes your question with other, similar questions. Using the right tags makes it easier for others to find and answer your question.

Type to find tags:
× 378
You need help with the use of the Stack Exchange API, apps built on the API, or assistance building scripts that work on Stack Exchange websites.
× 292
Indicates you've found an erroneous or unexpected behavior in the Stack Exchange API, or the Stack Exchange HTML or CSS, that needs to be fixed.
× 269
designed to solicit opinions or best-practices on a particular topic, with the goal of reaching community consensus.
× 256
Indicates that a feature request has been implemented, a bug has been fixed, or another type of request has been processed.
× 225
Applications that use the Stack Exchange API are listed as questions and tagged with this tag. The body of the question contains details and screenshots of the application.
× 224
indicates a proposal for a new feature for the Stack Exchange API, or a change to an existing feature.
× 158
for questions about the Stack Exchange API version 2.
× 151
User scripts for Stack Exchange sites that modify the site's behavior in the web browser. These scripts usually run in IE, Firefox, Chrome, Opera, and Safari.
× 144
A question about the Stack Exchange API: usage, functioning, guidelines, etc.
× 50
actually due to the existing design of the system and is not considered erroneous behaviour.
× 41
Question about any of the API methods that return, in some form, information about tags.
× 41
A question about the built-in API help pages at http://api.site.stackexchange.com/{version}/usage
× 41
Questions about usage of the Stack Exchange API in client-side browser JavaScript.
× 41
Libraries which provide access to the Stack Exchange API are listed under the [library] tag. The body of the question will give usage examples, as well as source and licensing details.
× 40
Indicates that a request (usually a feature request) has been considered, but will not be implemented. Generally speaking, a developer will leave a comment as to why, or the community will come to con…
× 36
Questions about searching via the API, typically using the /search method.
× 35
A question about how the API returns questions.
× 35
Question pertaining to the documentation provided with the API.
× 35
the centralized domain used for network-wide authentication to any site in the network.
× 35
A question tagged 'website' denotes that all or a part of the application is accessed via a web-interface.
× 33
A question about how the API returns reputation for users.
× 31
Accompanies [app]s written in, or [library]s meant to be used from, the Python programming language
× 30 × 29
Accompanies [app]s written in, or [library]s meant to be used from, the C# programming language
× 29
An [app] that takes the form of an extension to the Google Chrome browser.
× 25
A question about how the API returns users.
× 24
Indicates that the issue will be reviewed in the future, or that a change in functionality is being delayed until a future date.
× 24
A tip for developers working with the Stack Exchange API.
× 22
Questions about the registration, management, and usage of API keys.
× 22 × 22
Questions about per-site metas and the way in which they are exposed by the API.
× 21
Google's software stack for mobile devices. Please use the Android-specific tags such as [android-intent], not [intent]. For non-developer questions, see http://android.stackexchange.com
× 20
For questions relating to version 2.1 of the Stack Exchange API.
× 20
Accompanies [app]s written in, or [library]s meant to be used from, the Java programming language
× 20
Questions about the per-second or per-day rate limiting of requests made to the API.
× 19
Questions about whether [app]s with certain functionality exist. Some members of the community may react to these questions by creating those [app]s, should they not exist.
1 2 3 4 5 6