query type defines GraphQL operations to retrieve data from the server.
GraphQL queries are inherently hierarchical, composed from the
All queries commence at the root, serving as the schema's entry point. As you define a query, you can delve deeper into each object, requesting specific fields. This nested structure allows for precise data retrieval, letting you get as granular or as broad as you need. Therefore, by following the relationships between objects, you can craft queries of varying complexity. Unlike RESTful services, which might necessitate multiple round-trips (especially resource-intensive on mobile networks) or intricate SQL join statements, GraphQL naturally follows relationships between objects.
Fetches the currently authenticated user, often referred to as the viewer.
Initiates the retrieval of a user's membership to an organization, which can be further resolved via the
Serves as the primary entry point for all user-related queries.
Lookup a network by its
Arguments for network
The network identifier, a UUID string.
Paginate through all networks supported by the levain platform.
Arguments for networks
The number of items to return per page.
The forward cursor to start returning items from.
The backward cursor to start returning items from.
Optionally filter by the protocol type of the network.
Optionally filter by the network family of the network.
Retrieves the details of an asset.
Arguments for asset
The CAIP-19 asset identifier.
The CAIP-19 asset identifier. An alias for
The system-generated ID of the network asset.
Lookup an organization by its
All organization sub-queries are protected by a role-based authorization logic with different filter applied to different roles dependent of the user's role in the organization.
This is the root query for all organization-driven functionality with all other queries nested under this one.
Arguments for organization
A unique 12-digit identifier of an organization.
Lookup a wallet by its
Arguments for wallet
The system-generated unique ID of the wallet.