Lacking answers, I've suggested an edit to the api tag to clarify it's intended usage (code that implements and/or wraps an API, not code that uses one). Feel free to improve it further along those lines.

Allowing the tag to be used on any question containing code that simply talks to an API would make the tag way, way too broad. It would include just about anything talking to a web service and then some. So the next best thing is to limit its scope.

Good api fit:

• Implemeting API
• Wrapping existing API

Bad api fit:

• Any code that just happens to talk to an API but doesn't implement a new one or a wrapper for one

Feel free to start browsing through questions currently tagged with api and re-tag them. As usual, preferably not 20 at a time and make sure to give the question a good, critical look now we're at them anyway.

There are over 400 questions with the tag, but most of them aren't inappropriately tagged. So this won't have to take long.

Lacking answers, I've suggested an edit to the api tag to clarify its intended usage (code that implements and/or wraps an API, not code that uses one). Feel free to improve it further along those lines.

Allowing the tag to be used on any question containing code that simply talks to an API would make the tag way, way too broad. It would include just about anything talking to a web service and then some. So the next best thing is to limit its scope.

Good api fit:

• Implemeting API
• Wrapping existing API

Bad api fit:

• Any code that just happens to talk to an API but doesn't implement a new one or a wrapper for one

Feel free to start browsing through questions currently tagged with api and re-tag them. As usual, preferably not 20 at a time and make sure to give the question a good, critical look now we're at them anyway.

There are over 400 questions with the tag, but most of them aren't inappropriately tagged. So this won't have to take long.