9.7. Get Member Information
Get information about an existing team member.
| Method | URL Structure |
|---|---|
GET | /broker/rest/team/:id/member/:id |
Not applicable
$ curl -X GET https://openshift.redhat.com/broker/rest/team/5333d8b2a9429d1c3e0000ae/member/533369f861b322dfc1000003 --user user@example.com:password
The API returns the member resource with related resource links which have been left out for brevity. See Chapter 9, Members for more information on all member resource parameters.
{
"api_version": 1.6,
"data": {
"explicit_role": "view",
"id": "533369f861b322dfc1000003",
"links": {
"GET": {
"href": "https://openshift.redhat.com/broker/rest/team/5333d8b2a9429d1c3e0000ae/member/533369f861b322dfc1000003",
"method": "GET",
"optional_params": [
],
"rel": "Get member",
"required_params": [
]
},
},
"login": "member@example.com",
"owner": false,
"role": "view",
"type": "user"
},
"messages": [
{
"exit_code": 0,
"field": null,
"index": null,
"severity": "info",
"text": "Showing member 533369f861b322dfc1000003"
}
],
"status": "ok",
"supported_api_versions": [
1.0,
1.1,
1.2,
1.3,
1.4,
1.5,
1.6
],
"type": "member",
"version": "1.6"
}

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.