> For the complete documentation index, see [llms.txt](https://portal-integracao.intelbras.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://portal-integracao.intelbras.com.br/ct-5000-4pb/configuracao-de-usuarios/obter-todos-os-usuarios.md).

# Obter Todos os Usuários

### Obter Todos Usuários

Por meio da chamada abaixo é possível obter todos usuários.

#### Requisição - GET

`http://192.168.1.201/cgi-bin/recordFinder.cgi?action=doSeekFind&name=AccessControlCard&count=4300`

| param                  | type   | description                   |
| ---------------------- | ------ | ----------------------------- |
| `doSeekFind` \*        | String | Comando para Finalizar Buscar |
| `AccessControlCard` \* | Number | Registros que serão buscados  |
| `count` \*             | Number | Quantidade de registros       |

Também podemos usar o parâmetro Offset para a paginação da busca.

A paginação com base em offset e count é utilizada para obter registros a partir de um deslocamento específico. Em outras palavras, você indica o deslocamento a partir do qual deseja obter os dados por meio do offset e define o limite de registros a serem retornados por meio do parâmetro count.

#### Exemplo Offset:

`http://10.1.25.154/cgi-bin/recordFinder.cgi?action=doSeekFind&name=AccessControlCard&count=1024&offset=1024`

Conforme no exemplo a cima são obtidos os próximos 1024 usuários da lista.

#### Exemplo de Retorno - *text/plain*

```sh
found=3
records[0].CardName=test
records[0].CardNo=
records[0].CardStatus=0
records[0].CardType=0
records[0].CitizenIDNo=123456789012345678
records[0].Doors[0]=0
records[0].DynamicCheckCode=
records[0].FirstEnter=false
records[0].Handicap=false
records[0].IsValid=false
records[0].Password=234
records[0].RecNo=2
records[0].RepeatEnterRouteTimeout=4294967295
records[0].TimeSections[0]=255
records[0].UseTime=200
records[0].UserID=6
records[0].UserType=0
records[0].VTOPosition=
records[0].ValidDateEnd=2037-01-02 01:00:00
records[0].ValidDateStart=2019-01-02 00:00:00
records[1].CardName=test
records[1].CardNo=
records[1].CardStatus=0
records[1].CardType=0
records[1].CitizenIDNo=123456789012345678
records[1].Doors[0]=0
records[1].DynamicCheckCode=
records[1].FirstEnter=false
records[1].Handicap=false
records[1].IsValid=false
records[1].Password=234
records[1].RecNo=3
records[1].RepeatEnterRouteTimeout=4294967295
records[1].TimeSections[0]=255
records[1].UseTime=200
records[1].UserID=7
records[1].UserType=0
records[1].VTOPosition=
records[1].ValidDateEnd=2037-01-02 01:00:00
records[1].ValidDateStart=2019-01-02 00:00:00
records[2].CardName=test
records[2].CardNo=
records[2].CardStatus=0
records[2].CardType=0
records[2].CitizenIDNo=123456789012345678
records[2].Doors[0]=0
records[2].DynamicCheckCode=
records[2].FirstEnter=false
records[2].Handicap=false
records[2].IsValid=false
records[2].Password=234
records[2].RecNo=4
records[2].RepeatEnterRouteTimeout=4294967295
records[2].TimeSections[0]=255
records[2].UseTime=200
records[2].UserID=8
records[2].UserType=0
records[2].VTOPosition=
records[2].ValidDateEnd=2037-01-02 01:00:00
records[2].ValidDateStart=2019-01-02 00:00:00
```

#### Exemplos

{% tabs %}
{% tab title="Python" %}

```python
  import requests
 
device_ip = '10.1.35.144'
username = 'admin'
password = 'acesso1234'
 
url = "http://{}/cgi-bin/recordFinder.cgi?action=doSeekFind&name=AccessControlCard&count=4300".format(
                          str(device_ip),
                      )
 
digest_auth = requests.auth.HTTPDigestAuth(username, password)
rval = requests.get(url, auth=digest_auth, stream=True, timeout=20, verify=False)
print(rval.text)
```

{% endtab %}
{% endtabs %}

### Obter Número Total de Usuários Cadastrados

Por meio da chamada abaixo é possível obter o numero total de usuários cadastrados.

#### Requisição - GET

`http://192.168.1.201/cgi-bin/recordFinder.cgi?action=getQuerySize&name=AccessUserInfo`

| param                  | type   | description                                       |
| ---------------------- | ------ | ------------------------------------------------- |
| `AccessUserInfo` \*    | String | Comando para obter numero de Usuários cadastradas |
| `AccessControlCard` \* | Number | Registros que serão buscados                      |
| `count` \*             | Number | Quantidade de registros                           |

#### Exemplo de Retorno - *text/plain*

```sh
Size=1
count=1
```

#### Exemplos

{% tabs %}
{% tab title="Python" %}

```python
  import requests
 
device_ip = '10.1.35.144'
username = 'admin'
password = 'acesso1234'
 
url = "http://{}/cgi-bin/recordFinder.cgi?action=getQuerySize&name=AccessUserInfo".format(
                          str(device_ip),
                      )
 
digest_auth = requests.auth.HTTPDigestAuth(username, password)
rval = requests.get(url, auth=digest_auth, stream=True, timeout=20, verify=False)
 
print(rval.text)
```

{% endtab %}
{% endtabs %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://portal-integracao.intelbras.com.br/ct-5000-4pb/configuracao-de-usuarios/obter-todos-os-usuarios.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.