approov_service_flutter_httpclient library

Classes

ApproovClient
ApproovHttpClient
ApproovHttpClient is a drop-in replacement for the Dart IO library's HttpClient. If Approov is configured to protect an API on a host, then an ApproovHttpClient will automatically set up pinning and add relevant headers for a request, and also provide secret substitution if required. Otherwise the behaviour of ApproovHttpClient is the same as for the Dart IO library's HttpClient.
ApproovMessageSigning
Coordinates signature parameter factories across different hosts.
ApproovRequestMutations
Tracks request mutations applied during Approov request processing.
ApproovRequestSnapshot
Immutable snapshot of request metadata provided to mutator callbacks.
ApproovService
ApproovServiceMutator
Allows customization of Approov lifecycle and request processing behavior.
ApproovSigningContext
Holds the HTTP request data required for canonical signing.
ApproovTokenFetchResult
Result payload returned from an Approov fetch operation.
SignatureBaseBuilder
Builds canonical signature base strings from parameters and request context.
SignatureParameters
SignatureParametersFactory
Configures how signature parameters are generated for requests.

Enums

ApproovLogLevel
Service-layer logging levels for the Approov Flutter integration.
ApproovTokenFetchStatus
Potential status values returned by an Approov fetch operation.
SignatureDigest

Properties

Log → Logger
final

Exceptions / Errors

ApproovException
Base exception for Approov SDK and mutator related failures.
ApproovNetworkException
Exception indicating temporary network-related failures.
ApproovRejectionException
Exception carrying explicit rejection metadata from Approov.
RequiredBodyDigestException
Holds configuration for message signature parameters, mirroring the Swift implementation. Thrown when a body digest configured as required cannot be generated. One of only two deliberate fail-closed message signing conditions (mirroring approov-service-okhttp's RequiredBodyDigestException): the request must be aborted rather than sent without its required digest. Every other signing failure is fail-open - the request proceeds unsigned and the backend remains the enforcement point.
UnsupportedSignatureAlgorithmException
Thrown when the configured signing algorithm is unsupported or missing. The second deliberate fail-closed message signing condition (mirroring approov-service-okhttp, which fails closed via its unsupported-algorithm switch default): a misconfigured algorithm must abort the request rather than silently disable signing.