> ## Documentation Index > Fetch the complete documentation index at: https://docs.cdp.coinbase.com/llms.txt > Use this file to discover all available pages before exploring further. # List Accounts > Get a list of authenticated accounts for the current user. ## OpenAPI ````yaml GET /api/v3/brokerage/accounts openapi: 3.0.0 info: title: Coinbase Advanced Trade API version: '0.1' servers: - url: https://api.coinbase.com security: - apiKeyAuth: [] paths: /api/v3/brokerage/accounts: get: tags: - Accounts summary: List Accounts description: Get a list of authenticated accounts for the current user. operationId: RetailBrokerageApi_GetAccounts parameters: - name: limit description: >- The number of accounts to display per page. By default, displays 49 (max 250). If `has_next` is true, additional pages of accounts are available to be fetched. Use the `cursor` parameter to start on a specified page. in: query required: false schema: type: integer format: int32 - name: cursor description: >- For paginated responses, returns all responses that come after this value. in: query required: false schema: type: string - name: retail_portfolio_id description: >- **(Deprecated)** Only returns the accounts matching the portfolio ID. Only applicable for legacy keys. CDP keys will default to the key's permissioned portfolio. in: query required: false schema: type: string responses: '200': description: A successful response. content: application/json: schema: $ref: >- #/components/schemas/coinbase.public_api.authed.retail_brokerage_api.GetAccountsResponse text/event-stream: schema: $ref: >- #/components/schemas/coinbase.public_api.authed.retail_brokerage_api.GetAccountsResponse default: description: An unexpected error response. content: application/json: schema: $ref: '#/components/schemas/grpc.gateway.runtime.Error' text/event-stream: schema: $ref: '#/components/schemas/grpc.gateway.runtime.Error' components: schemas: coinbase.public_api.authed.retail_brokerage_api.GetAccountsResponse: type: object properties: accounts: type: array items: $ref: >- #/components/schemas/coinbase.public_api.authed.retail_brokerage_api.Account has_next: type: boolean example: true description: Whether there are additional pages for this query. required: - has_next cursor: type: string example: '789100' description: >- For paginated responses, returns all responses that come after this value. size: type: integer format: int32 description: Number of accounts returned required: - has_next grpc.gateway.runtime.Error: type: object properties: error: type: string code: type: integer format: int32 message: type: string details: type: array items: $ref: '#/components/schemas/google.protobuf.Any' coinbase.public_api.authed.retail_brokerage_api.Account: type: object properties: uuid: type: string example: 8bfc20d7-f7c6-4422-bf07-8243ca4169fe description: Unique identifier for account. name: type: string example: BTC Wallet description: Name for the account. currency: type: string example: BTC description: Currency symbol for the account. available_balance: description: Available balance in the account. allOf: - $ref: >- #/components/schemas/coinbase.public_api.authed.retail_brokerage_api.Amount default: type: boolean example: false description: Whether or not this account is the user's primary account active: type: boolean example: true description: Whether or not this account is active and okay to use. created_at: type: string format: RFC3339 Timestamp example: '2021-05-31T09:59:59.000Z' description: Time at which this account was created. updated_at: type: string format: RFC3339 Timestamp example: '2021-05-31T09:59:59.000Z' description: Time at which this account was updated. deleted_at: type: string format: RFC3339 Timestamp example: '2021-05-31T09:59:59.000Z' description: Time at which this account was deleted. type: example: FIAT description: What type the account is. allOf: - $ref: >- #/components/schemas/coinbase.public_api.authed.retail_brokerage_api.AccountType ready: type: boolean example: true description: Whether or not this account is ready to trade. hold: description: >- Amount that is being held for pending transfers against the available balance. allOf: - $ref: >- #/components/schemas/coinbase.public_api.authed.retail_brokerage_api.Amount retail_portfolio_id: type: string example: b87a2d3f-8a1e-49b3-a4ea-402d8c389aca description: The ID of the portfolio this account is associated with. platform: example: ACCOUNT_PLATFORM_CONSUMER description: >- Platform indicates if the account is for spot (CONSUMER), US Derivatives (CFM_CONSUMER), or International Exchange (INTX). allOf: - $ref: >- #/components/schemas/coinbase.public_api.authed.retail_brokerage_api.AccountPlatform google.protobuf.Any: type: object properties: type_url: type: string description: >- 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. value: type: string format: byte description: >- Must be a valid serialized protocol buffer of the above specified type. description: >- `Any` contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message. Protobuf library provides support to pack/unpack Any values in the form of utility functions or additional generated methods of the Any type. Example 1: Pack and unpack a message in C++. Foo foo = ...; Any any; any.PackFrom(foo); ... if (any.UnpackTo(&foo)) { ... } Example 2: Pack and unpack a message in Java. Foo foo = ...; Any any = Any.pack(foo); ... if (any.is(Foo.class)) { foo = any.unpack(Foo.class); } // or ... if (any.isSameTypeAs(Foo.getDefaultInstance())) { foo = any.unpack(Foo.getDefaultInstance()); } Example 3: Pack and unpack a message in Python. foo = Foo(...) any = Any() any.Pack(foo) ... if any.Is(Foo.DESCRIPTOR): any.Unpack(foo) ... Example 4: Pack and unpack a message in Go foo := &pb.Foo{...} any, err := anypb.New(foo) if err != nil { ... } ... foo := &pb.Foo{} if err := any.UnmarshalTo(foo); err != nil { ... } The pack methods provided by protobuf library will by default use 'type.googleapis.com/full.type.name' as the type URL and the unpack methods only use the fully qualified type name after the last '/' in the type URL, for example "foo.bar.com/x/y.z" will yield type name "y.z". JSON ==== The JSON representation of an `Any` value uses the regular representation of the deserialized, embedded message, with an additional field `@type` which contains the type URL. Example: package google.profile; message Person { string first_name = 1; string last_name = 2; } { "@type": "type.googleapis.com/google.profile.Person", "firstName": , "lastName": } If the embedded message type is well-known and has a custom JSON representation, that representation will be embedded adding a field `value` which holds the custom JSON in addition to the `@type` field. Example (for message [google.protobuf.Duration][]): { "@type": "type.googleapis.com/google.protobuf.Duration", "value": "1.212s" } coinbase.public_api.authed.retail_brokerage_api.Amount: type: object properties: value: type: string example: '1.23' description: Amount of currency that this object represents. required: - value currency: type: string example: BTC description: Denomination of the currency. required: - currency required: - value - currency coinbase.public_api.authed.retail_brokerage_api.AccountType: type: string enum: - ACCOUNT_TYPE_UNSPECIFIED - ACCOUNT_TYPE_CRYPTO - ACCOUNT_TYPE_FIAT - ACCOUNT_TYPE_VAULT - ACCOUNT_TYPE_PERP_FUTURES default: ACCOUNT_TYPE_UNSPECIFIED title: Account type defines the type of account that is supported coinbase.public_api.authed.retail_brokerage_api.AccountPlatform: type: string enum: - ACCOUNT_PLATFORM_UNSPECIFIED - ACCOUNT_PLATFORM_CONSUMER - ACCOUNT_PLATFORM_CFM_CONSUMER - ACCOUNT_PLATFORM_INTX default: ACCOUNT_PLATFORM_UNSPECIFIED securitySchemes: apiKeyAuth: type: http scheme: bearer bearerFormat: JWT description: >- A JWT signed using your CDP API Key Secret, encoded in base64. Refer to the [Creating API Keys](/coinbase-app/authentication-authorization/api-key-authentication) section of our Coinbase App Authentication docs for information on how to generate your Bearer Token. ````