2

I'm considering using the API for a retag job not supported by existing tooling as per this meta post (of course, I'll make sure the community supports the effort before going forward).

I'm planning to use Py-StackExchange (didn't yet looked into details, so may have to consider something else if it doesn't support retagging; also considered FixAllTheTags but it doesn't allow to set an edit summary)

The problem is: since I'll need write access, I'm going to have to register a Stack App to get an API key. For which, I'll need to provide an app's name, functionality, where it's hosted, its official site, etc.

But, none of that is applicable to my use case. It won't be a web app, nor am I going to let arbitrary users use it, or make an official site and arrange its hosting, all just for the sake of a few hours' work. Nor is there a name or a predefined set of functionality - it's going to just be various odd jobs from time to time as the need arises.

How shall I go about this?

Improve this question

1 Answer 1

Reset to default
1

I think you can just create an and mark it as a . Those are

for apps that don't quite work yet, but need a registered Stack Apps post for testing.

Incomplete posts are allowed for placeholder apps, so you don't need to fill in all the details. While this might be bending the rules a bit, as long as it doesn't cause an avalanche of placeholder apps, it's probably fine.

Improve this answer
2
  • Since this "app" is never going to go out of the "placeholder" stage, I'm probably required to delete the post once I am done with this particular job, am I not? Or that is clearly going to be an abuse of the tag. And an exact scenario for "avalanche of placeholder apps" since every user potentially has the same needs (with Data.SE, one can read but not write, so there's little need to use API for one-off tasks if you aren't going to write).
    – ivan_pozdeev
    Commented Sep 4, 2017 at 14:35
  • @ivan_pozdeev we've added that requirement after lots of people came here following a certain tutorial. I think most of those people weren't really interested in Stack Exchange; they just wanted to experiment with an Android app. That warning wasn't meant for 'serious' developers using the Stack Exchange API.
    – Glorfindel ♦
    Commented Sep 4, 2017 at 14:54

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .