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.
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.
Use this ONLY to list or announce your application; and ONLY if that application either uses the Stack Exchange API or works on any of the Stack Exchange websites. See stackapps.com/q/7/ for more info…
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.
Questions about the Stack Exchange API *only*. If your question concerns any other API, do not use this tag. For bugs, please (also) use the version tag, EG [api-v2.2], that the bug applies to.
to post a userscript that operates on Stack Exchange sites and/or uses the Stack Exchange API. For questions about user scripting and Stack Exchange, or its API, use the [scripts] tag in…
designed to solicit opinions or best-practices on a particular topic, with the goal of reaching community consensus.
Indicates that a feature request has been implemented, a bug has been fixed, or another type of request has been processed.
indicates a proposal for a new feature for the Stack Exchange API, or a change to an existing feature.
for questions about the Stack Exchange API version 2. First released Feb 2012.
For questions relating to version 2.2 of the Stack Exchange API.
Tools that help with questions, or issues with the API handling of questions.
Question pertaining to the documentation provided with the API.
For apps that don't quite work yet, but need a registered Stack Apps post for testing. If you're following a tutorial which asks to post a placeholder app here, that's fine, but please delete it after…
Tools that help with user profiles/accounts, or issues with the API handling of users
Tools that help with tags, or issues with the API handling of tags.
A question about the Stack Exchange authentication process and related API methods.
Apps, Scripts, Libraries, Bugs, Feature-requests, or APIs that are: deprecated, no longer available/supported, or no longer relevant.
Questions about, or scripts/apps/libraries that enhance Stack Exchange's Chat rooms/feature.
For *either* meta questions about Stack Apps, or about how per-site metas are exposed by the API. (Stack Apps is its own meta site)
Apps accessible using web interfaces should use this tag. Questions about SE sites really shouldn't.
Questions about searching via the API, typically using the /search method.
Questions handling comments using the API. Or, posts of Scripts / Apps / Libraries that facilitate dealing with comments on Stack Exchange sites.
to POST, or announce, libraries which provide access to the Stack Exchange API and/or Stack exchange sites. The body of the question will give usage examples, as well as source and licen…
Tools (scripts/apps/libraries) that help with answers, or issues with the API handling of answers
User reputation as returned by the API or displayed on Stack Exchange sites
For questions relating to authenticating with the Stack Exchange API using OAuth 2.0, which is an open standard for authorization. General OAuth 2.0 questions are off-topic but might find a home elsew…
actually due to the existing design of the system and is not considered erroneous behaviour.
Questions about the built-in API **HELP PAGES** at api.stackexchange.com/docs. For issues with the API itself, use the [api] tag, not this tag.
Questions about the registration, management, and usage of API keys.
Accompanies [app]s written in, or [library]s meant to be used from, the Python programming language
An [app] that takes the form of an extension to the Google Chrome browser.
For questions about either API methods for editing posts, or for tools/apps/scripts that enhance the editing experience.
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.