The WaaS APIs follow the conventions established by Google's API Improvement Proposals (AIPs). This means that WaaS APIs exhibit resource-oriented design per AIP-121, providing individually-named resources (nouns) and the relationships and hierarchy that exist between them.
The resources provided by WaaS APIs are composable and interoperable. For example:
Networkresource provided by the Blockchain Service is an argument to APIs in the Protocol Service and WalletService.
Keyresource provided by the Key Service is used by Wallet Service APIs.
Consider the following string, which represents a BIP-32 HD Wallet in Wallet Service:
We parse this string as follows:
| ||pool||resource ID|
| ||wallet||resource ID|
We use this terminology throughout our API documentation to disambiguate between different segments of a resource name.
Customers can set an identifier (as in
pool-identifier) to an arbitrary string. If not set, it defaults to a UUID.
Was this helpful?