5

This is fixed. I was able to pin down the issue two web servers. After SRE verified that the URL length settings were fine, I was able to narrow the issue to individual path components over the IIS default of 260 characters as described in https://stackoverflow.com/a/16903689/860000. SRE confirmed that UrlSegmentMaxLength was correct so there was only one ...


2

You can't just edit the tags via the API, you have to set the body as well. For that, you need the Markdown (the body_markdown field in the filter) instead of the HTML:


1

An access_token is not enough; you need to specify a value for key as well. You can find it in the entry for your app here, this is how it looks like for one of mine: I'm not sure how it works in JavaScript, but in cases like yours the API will send error details in the body; your library may ignore it by default if the HTTP code indicates an error, but it'...


1

I can reproduce (sort of): Search on the main site: 1,449 results Searching with the API: 857 results I use a different filter which shows the total number of results at the bottom, but that doesn't matter: What happens here is explained in the API documentation, if you look closely: Usage of /search/advanced GET Discussion Searches a site for any ...


1

Why is my app post deleted? My guess is that an automated process did this. You can still view the post, just copy the URL from the 'Manage your applications' page. If it has a banner 'deleted by Community ♦' that's the case. Should I just create a new post to get API access? That's fine (it's not that we're flooded with new posts every day). Something ...


1

There's indeed no difference between order=asc and order=desc; perhaps this is a limitation of Elasticsearch which powers the Stack Exchange search engine (both the API and on the sites). To be fair, to find the most irrelevant search result on the site you have to go to the last page yourself. The API is no different. There is some difference between the ...


1

Yes, you're already doing the right thing by batching the requests to minimize the number of API calls (just group them in groups of 30 or so) but you're still limited to 300 requests per day, as per How API Keys Work (FAQ). You have to register your application (you don't even need to authenticate your user) to get a request key for it, and using that will ...


1

For posting comments, you need a request key for your application: Applications should be registered on Stack Apps to get a request key. Request keys grant more requests per day, and are necessary for using access_tokens created via authentication. You need to enable write access for your application. I think you can use this question as registered Stack ...


Only top voted, non community-wiki answers of a minimum length are eligible