> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-api/user-api/backend-api/resources/commons/subuser/places.md).

# Subuser places

## API actions

API path: `/subuser/places`.

### bind

Gives access for sub-user to specified places.

**required tariff features:** `multilevel_access` – for ALL trackers.**required sub-user rights:** `admin` (available only to master users).

#### Parameters

| name            | description                                                                                                        | type      |
| --------------- | ------------------------------------------------------------------------------------------------------------------ | --------- |
| subuser\_id     | ID of a sub-user belonging to current account.                                                                     | int       |
| access\_to\_all | Optional. If `true` then sub-user will have access to all places of master user.                                   | boolean   |
| place\_ids      | Optional. List of place IDs to associate with a specified sub-user. All places must belong to current master user. | int array |

> At least one of **access\_to\_all** and **place\_ids** parameters must be not null.

#### Examples

cURL

{% code overflow="wrap" %}

```sh
curl -X POST 'https://api.eu.navixy.com/v2/subuser/places/bind' \
    -H 'Content-Type: application/json' \
    -d '{"hash": "22eac1c27af4be7b9d04da2ce1af111b", "subuser_id": 204951, "access_to_all": false, "place_ids": [7548]}'
```

{% endcode %}

#### Response

```json
{
  "success": true
}
```

#### Errors

* 13 – Operation not permitted – if user has insufficient rights.
* 201 – Not found in the database – if sub-user/place does not exist or does not belong to current master user.
* 236 – Feature unavailable due to tariff restrictions (if there is at least one tracker without `multilevel_access` tariff feature).

### unbind

Disables access for a sub-user to specified places.

**required tariff features:** `multilevel_access` – for ALL trackers.**required sub-user rights:** `admin` (available only to master users).

#### Parameters

| name        | description                                                                                              | type      |
| ----------- | -------------------------------------------------------------------------------------------------------- | --------- |
| subuser\_id | ID of a sub-user belonging to current account.                                                           | int       |
| place\_ids  | List of place IDs to associate with a specified sub-user. All places must belong to current master user. | int array |

#### Examples

cURL

{% code overflow="wrap" %}

```sh
curl -X POST 'https://api.eu.navixy.com/v2/subuser/places/unbind' \
    -H 'Content-Type: application/json' \
    -d '{"hash": "22eac1c27af4be7b9d04da2ce1af111b", "subuser_id": 204951, "place_ids": [7548]}'
```

{% endcode %}

#### Response

```json
{
  "success": true
}
```

#### Errors

* 13 – Operation not permitted – if user has insufficient rights.
* 201 – Not found in the database – if sub-user/place not exist or does not belong to current master user.
* 236 – Feature unavailable due to tariff restrictions (if there is at least one tracker without `multilevel_access` tariff feature).

### list\_ids

Gets a list of place IDs to which this sub-user has access.

**required tariff features:** `multilevel_access` – for ALL trackers.**required sub-user rights:** `admin` (available only to master users).

#### Parameters

| name        | description                                    | type |
| ----------- | ---------------------------------------------- | ---- |
| subuser\_id | ID of a sub-user belonging to current account. | int  |

#### Examples

cURL

```sh
curl -X POST 'https://api.eu.navixy.com/v2/subuser/places/list_ids' \
    -H 'Content-Type: application/json' \
    -d '{"hash": "22eac1c27af4be7b9d04da2ce1af111b", "subuser_id": 204951}'
```

#### Response

```json
{
  "success": true,
  "access_to_all": true,
  "list": [7548]
}
```

#### Errors

* 13 – Operation not permitted – if user has insufficient rights.
* 201 – Not found in the database – if sub-user with such an ID does not exist or does not belong to current master user.
* 236 – Feature unavailable due to tariff restrictions (if there is at least one tracker without `multilevel_access` tariff feature).

### list

Gets a list of places to which this sub-user has access.

**required tariff features:** `multilevel_access` – for ALL trackers.**required sub-user rights:** `admin` (available only to master users).

#### Parameters

| name        | description                                                                                                                                     | type                                                        |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| subuser\_id | ID of a sub-user belonging to current account.                                                                                                  | int                                                         |
| filter      | Optional. Filter for place label, description, address, external ID and custom fields.                                                          | string                                                      |
| tag\_ids    | Optional. Tag IDs assigned to places. Places found must include all tags from a list.                                                           | int array                                                   |
| offset      | Optional. Offset from start of found places for pagination.                                                                                     | int                                                         |
| limit       | Optional. Limit of found places for pagination.                                                                                                 | int                                                         |
| order       | Optional. Specify list ordering. Can be any of `id`, `label`, `description`, `location`, `external_id`, `assigned_date`. Default order by `id`. | [enum](/docs/navixy-api/user-api/backend-api.md#data-types) |

#### Examples

cURL

{% code overflow="wrap" %}

```sh
curl -X POST 'https://api.eu.navixy.com/v2/subuser/places/list' \
    -H 'Content-Type: application/json' \
    -d '{"hash": "22eac1c27af4be7b9d04da2ce1af111b", "subuser_id": 204951, "offset": 0, "limit": 1000}'
```

{% endcode %}

#### Response

```json
{
  "success": true,
  "access_to_all": false,
  "list": [<place>, ...],
  "count": 12
}
```

#### Errors

* 13 – Operation not permitted – if user has insufficient rights.
* 201 – Not found in the database – if sub-user with such an ID does not exist or does not belong to current master user.
* 236 – Feature unavailable due to tariff restrictions (if there is at least one tracker without `multilevel_access` tariff feature).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://navixy.com/docs/navixy-api/user-api/backend-api/resources/commons/subuser/places.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.