Re: Feedback 2017-08-12


Hi James,

On Sat, Aug 12, 2017 at 2:41 PM, James Milligan <james@...> wrote:
Just a few things I've picked up this evening:

API errors consistently getting BAD_REQUEST with this one despite a valid group_id set ( that the calling user has access to (as an owner). Originally thought it might be because of 0 topics/messages, but even after adding a couple of messages to the group I'm still getting the same response (repro'd with Postman to skip the Java client).

Sorry about that. That endpoint should be considered not implemented right now (and the docs are wrong). I've just added the 'NI' in the docs for that.

(Generally) example schemas don't always tally with response attribute listings, mostly just a case of some missing fields. I'm using the schemas to generate POJOs which means I'm sometimes missing a couple of attributes.

Good catch. I will update the examples on Monday.

(Generally) some required tags missing orange label formatting

I see that in the get topics endpoint, which I'll fix next week. Please let me know if you see them anywhere else.

(Suggestion) displaying requirements for calls in a consistent way - permissions, plan levels, and required params. is missing mandatory group_id param in example request missing comma after time_pref value (invalid JSON)

These are fixed.


Join to automatically receive all group messages.