Search Results

This is a documentation bug in my opinion. The "via Example App" was never included, nor should it be. …

The authentication doc page now lists URL's like: https://stackoverflow.com/oauth https://stackoverflow.com/oauth/access_token etc. While these seem to work, the correct domain is stackexchange.co …

Note that version 2.3 has been around since at least Aug 28, 2015 (Date of that answer). I could have sworn that one of the SE guys said they weren't going to document it, but can't find a reference …

Yes, you must provide all three of: tags, title, and body -- even if they haven't changed. Otherwise you will get error messages like: "error_id": 400, "error_message": "tags", "error_name": "bad …

The documentation still needs to be corrected. …

The key mistake here is neglecting the Wrapper Object, and this is a big flaw with the filter documentation. The wrapper is the box that everything you get from the API comes in. …

Strictly speaking, that line is incorrect. The method will always return a JSON object (barring certain server failures). But the items array will be empty or missing. On success, the default objec …

The documentation was updated sometime in the last 2 years and the API docs (version 2.2) now state that the property may be absent: …

The link is correct. The purpose of that control is to provide a URL to the doc page with all the parameters prefilled. This is what most users expect and is similar to how that link control works o …

Yes, officially this is a documentation bug. From the Absent Fields doc: Fields that are not always guaranteed to be set... are indicated in the per-type documentation. … Any discrepency(sic) between observed behavior and the documentation should be reported on Stack Apps. …

RE: Is site the api_site_parameter of the site object? Yes.   Although as stated in the "Per-Site Methods" section of the main doc page, you can also use the full domain name, EG cooking.stackexchan …

This is exactly how it should be (except that the doc page might be more explicit). The meta_site parameter refers to Per-site Metas. Meta Stack Exchange is not a per-site meta. Think of it as a …

Yes, if you omit those parameters it will give you the expected result... If a valid token is passed, then it will return the user ("There can be only one.") who obtained/approved that token. For thi …

This is either a bug with the route or an omission in the documentation. Workaround: Use the /search or the /search/advanced routes, with a filter that just returns total. …

This is a very minor bug in the documentation page. The online doc page adds a convenient hyperlink to the post (The link part is not in the API's JSON response). That's a good thing. … As for the rest, the documentation clearly says: post_id 2.1       integer, refers to a post, may be absent (Emphasis added) post_id is present only when the notification refers to a specific post …