Get one account user

Overview

Get a user's details and access.

Use this to check or edit.

You'll need the user_id.

Returns the user. location and accounts come as {value, label} pairs, ready to pre-fill a form; user_type is the value to send back when you edit the user.

Prerequisites

A bearer token. See Authentication.
The user's id (user_id), from List users.

Base URL

Environment	URL
Production	`https://production-api.shoutaboutus.com`
Development	`https://development-api.shoutaboutus.com`

Endpoint

POST /api/v1/user/get

Authentication

Partner or Account token

user_id must be a user inside your own account tree. A Partner token can get users in any account under the partner; an Account token only users in its own account.
A user outside your tree is rejected with 422.

Rate limit

This endpoint has no rate limit.

Request parameters

None.

Request body

Field	Type	Required	Notes
`user_id`	integer	Yes	The user to get. Must exist and be inside your account tree.

Request payload

{
  "user_id": 3011
}

Response body

The payload is inside data.

Field	Type	Description
`status`	string	`success`.
`response`	object	The user.
`response.id`	integer	The user's id.
`response.first_name`	string	First name.
`response.last_name`	string or null	Last name.
`response.email`	string	The user's email address.
`response.inactive_at`	string or null	When the user is (or was) deactivated. `null` when no deactivation date is set.
`response.email_verified_at`	string or null	When the user's email address was verified.
`response.title`	string or null	Job title.
`response.user_type`	string	`admin`, `location_assign`, `assign_brand` or `basic`: the value to send as `user_type` when you edit the user.
`response.role`	string	The user's role label: `Owner`, `Admin User`, `Brand Assigned`, `Location Assigned`, `Basic User` or `User`.
`response.location`	array	The locations assigned to the user. Empty when none are assigned.
`response.location[].value`	integer	The location's id.
`response.location[].label`	string	The location's name, followed by `-` and its `client_location_id` (or its `storeid` when it has no `client_location_id`).
`response.accounts`	array	The accounts assigned to the user. Empty when none are assigned.
`response.accounts[].value`	integer	The account's id.
`response.accounts[].label`	string	The account's name, followed by `-` and your own account id (`client_account_id`) when it has one.

Response payload

{
  "data": {
    "status": "success",
    "response": {
      "id": 3011,
      "first_name": "Jane",
      "last_name": "Smith",
      "email": "[email protected]",
      "inactive_at": null,
      "email_verified_at": "2026-09-23T10:43:43.000000Z",
      "title": "Manager",
      "user_type": "admin",
      "role": "Owner",
      "location": [],
      "accounts": []
    }
  }
}

Examples

Success payload

A user limited to one location:

{
  "data": {
    "status": "success",
    "response": {
      "id": 12,
      "first_name": "Jane",
      "last_name": "Smith",
      "email": "[email protected]",
      "inactive_at": null,
      "email_verified_at": "2026-06-16T12:26:09.000000Z",
      "title": "Manager",
      "user_type": "location_assign",
      "role": "Location Assigned",
      "location": [
        {
          "value": 3007,
          "label": "Downtown Store - LOC-12"
        }
      ],
      "accounts": []
    }
  }
}

Error payload

422 User outside your tree

{
  "message": "The selected user id does not belong to your company hierarchy.",
  "errors": {
    "user_id": [
      "The selected user id does not belong to your company hierarchy."
    ]
  }
}

422 user_id missing

{
  "message": "The user id field is required.",
  "errors": {
    "user_id": [
      "The user id field is required."
    ]
  }
}

Status	Meaning
`200`	The user.
`401`	The token is missing, expired or invalid.
`422`	`user_id` is missing, doesn't exist, or is outside your tree.
`500`	Unexpected server error.

Example request

curl --request POST \
  --url "https://production-api.shoutaboutus.com/api/v1/user/get" \
  --header 'Authorization: Bearer <bearer-token>' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --data '{"user_id": 3011}'

Updated 17 days ago

Did this page help you?