---
title: "Accounts returns all the existing accounts."
method: GET
path: "/cosmos/auth/v1beta1/accounts"
tags: ["Query"]
---

# Accounts returns all the existing accounts.

`GET /cosmos/auth/v1beta1/accounts`

When called from another module, this query might consume a high amount of
gas if the pagination field is incorrectly set.

Since: cosmos-sdk 0.43

## Query parameters

- `pagination.key` string, byte
- `pagination.offset` string, uint64
- `pagination.limit` string, uint64
- `pagination.count_total` boolean
- `pagination.reverse` boolean

## Response `200`

A successful response.

- CosmosAuthV1beta1QueryAccountsResponse — QueryAccountsResponse is the response type for the Query/Accounts RPC method. Since: cosmos-sdk 0.43
  - `accounts` GoogleProtobufAny[]
    - `@type` string — A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in `path/google.protobuf.Duration`). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme `http`, `https`, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: * If no scheme is provided, `https` is assumed. * An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one. Schemes other than `http`, `https` (or the empty scheme) might be used with implementation specific semantics.
  - `pagination` CosmosBaseQueryV1beta1PageResponse — PageResponse is to be embedded in gRPC response messages where the corresponding request message has used PageRequest. message SomeResponse { repeated Bar results = 1; PageResponse page = 2; }
    - `next_key` string, byte — next_key is the key to be passed to PageRequest.key to query the next page most efficiently. It will be empty if there are no more results.
    - `total` string, uint64

## Other responses

- `default` — An unexpected error response.

---

[API](https://skmtc.net/coreumfoundation/apis/title-goes-here.md) · [All operations](https://skmtc.net/coreumfoundation/apis/title-goes-here/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/coreumfoundation/title-goes-here/revisions/2a2e5bc4593a/schema)