Search Results

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 …

After re-investigating my code, I realized what was going on here. For this particular project I wasn't using the API key and access token of my own application; I'm using the ones I sniffed from the …

In this URL: https://api.stackexchange.com/2.2/questions/unanswered/?team_url=stackoverflow.com%2fc%2ffoosite&site=stackoverflow&key=u9eRD30bklGv9t9gzDRSAQ(( you're passing a team_url parameter. That' …

You already have the correct URL. The access token is valid for all sites, even those for which you don't have an account. The documentation explains how to switch to a different site than Stack Overf …

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' …

It looks like a bug in the API. It looks like it filters on the creation date of the question, not the timeline events themselves. The question has a timestamp of 1596793060, and using a fromdate of 1 …

No, this information is not exposed via the API (and it's not available in SEDE either). At the moment, your best bet is probably to scrape the tag notifications page, though this only works for your …

It's not possible (short of fetching all users and filtering yourself). The API simply does not offer that query. For alternatives, see the Data Explorer (SEDE): https://meta.stackexchange.com/q/25372 …

From the registration page: Why Register? Because it's the neighborly thing to do. We like to know who is using our API, and how, so we can have the metrics we need to support your application and im …

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, …

It is indeed possible to use custom URL schemes for authentication in an iOS app. Here are the steps I took: Choose an arbitrary domain, like stackexchange.com, for the OAuth domain in your Stack App …

You can – sometimes. The default filter contains a question_id field, and according to the examples for the inbox_item type (you have to scroll down a bit) it is filled in some situations. I just test …

This is not an official API, but it is not too hard to simulate the login via OAuth2 and use the session to start executing a query, poll the job that executes it and retrieve the results in the end. …

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:

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 Jav …