Google Cloud Client Libraries for Rust - Dialogflow API

WARNING: some RPCs have no corresponding Rust function to call them. Typically these are streaming RPCs. We expect adding these RPCs in a way that does not break the existing APIs or changes their behavior in a significant way. We do anticipate a number of new crate dependencies will be required. If you need these RPCs please open an issue in our GitHub repository.

Builds conversational interfaces (for example, chatbots, and voice-powered apps and devices).

The client library types and functions are stable and not expected to change. Please note that Google Cloud services do change from time to time. The client libraries are designed to preserve backwards compatibility when the service changes in compatible ways. For example, adding RPCs, or fields to messages should not introduce breaking changes to the client libraries.

Quickstart

The main types to work with this crate are the clients:

• Agents: enabled by the agents feature.
• AnswerRecords: enabled by the answer-records feature.
• Contexts: enabled by the contexts feature.
• Conversations: enabled by the conversations feature.
• ConversationDatasets: enabled by the conversation-datasets feature.
• ConversationModels: enabled by the conversation-models feature.
• ConversationProfiles: enabled by the conversation-profiles feature.
• Documents: enabled by the documents feature.
• EncryptionSpecService: enabled by the encryption-spec-service feature.
• EntityTypes: enabled by the entity-types feature.
• Environments: enabled by the environments feature.
• Fulfillments: enabled by the fulfillments feature.
• Generators: enabled by the generators feature.
• GeneratorEvaluations: enabled by the generator-evaluations feature.
• Intents: enabled by the intents feature.
• KnowledgeBases: enabled by the knowledge-bases feature.
• Participants: enabled by the participants feature.
• Sessions: enabled by the sessions feature.
• SessionEntityTypes: enabled by the session-entity-types feature.
• SipTrunks: enabled by the sip-trunks feature.
• Tools: enabled by the tools feature.
• Versions: enabled by the versions feature.

Features

• default-rustls-provider: enabled by default. Use the default rustls crypto provider (aws-lc-rs) for TLS and authentication. Applications with specific requirements for cryptography (such as exclusively using the ring crate) should disable this default and call rustls::crypto::CryptoProvider::install_default().
• Each client can be enabled using its own feature. Use the client's name in kebab-case to enable the client.

More Information

• Read the crate's documentation