Time  Nick     Message
23:49 squib0   and I'm learning that this was a false expectation
23:49 squib0   I was thinking that when I narrow down my GET by saying ?isCustom=True , that the API would return whatever objects had that key:value pair associated with it. so I was expecting isCustom:True to be an actual part of the records returned
23:49 whartung I’m sorry, I have to leave…have a good weekend…(I’ll be back on monday…)
23:47 whartung it will return what you want it to return, and (ideally) what it’s documented to return. What do you want it to do?
23:47 squib0   sorry if these are stupid questions, I'm very new to programming
23:47 squib0   and the response will not necessarily contain the key:value requested
23:46 whartung yes
23:46 squib0   is it that in the api documentation it will tell you the params available and it will return whatever is documented?
23:46 whartung how so?
23:45 squib0   whartung, there probably is, but I think I am having a general misunderstanding of the relationship between a param and what's contained in the response
23:23 whartung you mean there’s no way looking at the resource representation to discover if it is a “custom” application?
23:10 squib0   can an API store attributes that are not returned?
23:10 squib0   so I'm wondering how I would have parsed the full object list for a custom application if I hadn't supplied that isCustom param
23:09 squib0   that works, it narrows down the objects. but that attribute isn't stored in the response
23:09 squib0   so if I GET https://url/api/v1/appication?isCustom=True
23:08 squib0   one of the available params is {isCustom:True}
23:08 squib0   a GET returns a list of all application objects of course
23:08 squib0   so I have an api  at https://url/api/v1/application
23:07 squib0   hey guys very new to APIs here.