# User data needed parameter

**URL:** <https://community.trooptrack.com/t/user-data-needed-parameter/3009>\
**Category:** The TroopTrack Developer Program\
**Created:** [September 14, 2016, 9:48pm UTC](https://community.trooptrack.com/t/user-data-needed-parameter/3009 "2016-09-14T21:48:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![GreggOrangio](https://avatars.discourse-cdn.com/v4/letter/g/34f0e0/32.png) [@GreggOrangio](https://community.trooptrack.com/u/GreggOrangio)\
**Post date:** [September 14, 2016, 9:48pm UTC](https://community.trooptrack.com/t/user-data-needed-parameter/3009/1 "2016-09-14T21:48:09Z")

</div>

## As a new TT API user, I immediately inspected the User data requests which we hope to utilize for interfacing our custom roster and event management system. In doing so, it appears that a key piece of data is missing for each user record. That is a household identifier. As far as I can see, there is no way to accurately link users into a household aside from matching surnames which of course can be error prone. Did I miss something? Is there another method that is recommended?

---

<div class="post-metadata">

**Author:** ![dave](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.trooptrack.com/dave/32/13_2.png) [@dave](https://community.trooptrack.com/u/dave)\
**Post date:** [September 14, 2016, 10:08pm UTC](https://community.trooptrack.com/t/user-data-needed-parameter/3009/2 "2016-09-14T22:08:24Z")

</div>

@GreggOrangio, the users endpoint does not include household info, but the users/id endpoint does. Give that a try please.

~ Dave

---

<div class="post-metadata">

**Author:** ![GreggOrangio](https://avatars.discourse-cdn.com/v4/letter/g/34f0e0/32.png) [@GreggOrangio](https://community.trooptrack.com/u/GreggOrangio)\
**Post date:** [September 15, 2016, 10:47am UTC](https://community.trooptrack.com/t/user-data-needed-parameter/3009/3 "2016-09-15T10:47:01Z")

</div>

OK, thanks for the quick reply @dave.

## So studying the API and data a bit more, it seems that the /users endpoint was not designed as I had expected it would be. Admittedly I’m not sure of the original design requirements. What I am saying is that the returned data does not provide data to build “typical” rosters where youth information is tied or totally dependent upon parents/households. For example, I don’t see how to reasonably construct a contact list for an entire Troop or subgroups. I see it can be done by one call to /users followed by repeated calls to /users/{id}, but… Again, am I missing something?

---

<div class="post-metadata">

**Author:** ![dave](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.trooptrack.com/dave/32/13_2.png) [@dave](https://community.trooptrack.com/u/dave)\
**Post date:** [September 15, 2016, 3:12pm UTC](https://community.trooptrack.com/t/user-data-needed-parameter/3009/4 "2016-09-15T15:12:03Z")

</div>

You’re not missing anything. If you want to get the household details you will need to make multiple calls.