At this page the documentation states that detailed record for user can be obtained by GET /admin/users/{id}.json Tests suggest this is not correct (returns 404) and the correct URL is GET /admin/users/{id}/{username}.json Should I do a PR on the docs repo? Or do the team consider that the API expresses what the API should do, so this is actually an API bug? Julian

Sorry @Mittineague I’m absolutely positive. Maybe this is a version change? I am running against Discourse 2.1.1 You can also see it -in the UI - when you look at details of a user they appear at //admin/users/{userid}/{username} while //admin/users/{userid}/ is a 404

You have a few variations there. These work for me. Discourse 2.2.0.beta2 .../admin/users/{userid}.json .../admin/users/{userid}/{username} .../admin/users/{userid}/{username}.json

[image] Mittineague: …/admin/users/{userid}.json That one works for me too. I’ve been ignoring the .json suffix and just using the header as documented Instead of sending API requests to /categories.json you may also send them to /categories and add an Accept: application/json header to the request to get the JSON response. Sending requests with the Accept header is necessary if you want to use URLs for related endpoints returned by the API, such as pagination URLs. These URLs are returned without the .json prefix so you need to add the header in order to get the correct response format. but maybe I need to change my code to use it.

Routing is different for different paths. Do you have the Ember addon installed in your browser? [image] Installing the Inspector - Ember Inspector - Ember Guides You can install the Inspector on Google Chrome, Firefox, other browsers (via a bookmarklet), and on mobile devices by following the steps below. Google Chrome You can install the Inspector on Google Chrome as a new Developer Tool. To begin, visit...

[image] Mittineague: Routing is different for different paths. Do you have the Ember addon installed in your browser? I have now - so this is about reverse engineering the API?

API documentation error?

Development

Mittineague (Mittineague) September 20, 2018, 8:12am 2

I think you should revisit your tests. The first path works fine as long as it is a valid member id number

In fact, AFAIK, it is the only path that works with the account number and not the member name.

Topic		Replies	Views
Requested url error in 'Get a user by id' Development rest-api	1	336	March 9, 2023
API Returning HTML Instead of JSON At Specific Routes? Development	3	9512	November 21, 2018
/u.json not working Product Support	6	657	March 15, 2020
Refreshing a users detail page in admin doesn't work in some cases Bug	2	1267	October 12, 2016
Potential API bug - "Get a public list of users" endpoint Bug rest-api	4	840	August 11, 2020

API documentation error?

Related topics