Retrieve a staff member
One team member, in the same shape the list serves, so an id read off a conversation can be resolved on its own rather than by paging the whole roster. THE PATH TAKES THE USER ID, which is this resource’s own id and the value assigned_to and author_user_id carry. A membership record id is not accepted and is never published. THE 404 IS THE ANSWER, not merely the error case. “Is this id still a member of my store” is exactly the check to make before writing it to a conversation’s assigned_to, where the same question is asked again and the write is refused. A user id belonging to another store is a 404 here, the same way that member is invisible in the list.
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Path Parameters
Response
Success
