///
While the Quicksilver SDK emphasizes a fluent Domain-Specific Language (DSL) and active models for common interactions, it also exposes the underlying resource classes (`src/resources/*`) for direct R
49 views
~49 views from guests
Guest views are estimated from total page views. These include anonymous visitors and users who weren't logged in when they viewed the page.
While the Quicksilver SDK emphasizes a fluent Domain-Specific Language (DSL) and active models for common interactions, it also exposes the underlying resource classes (src/resources/*) for direct REST API calls. These classes are primarily used internally by the active models (like API Reference: Account Model and API Reference: Transaction Model) and the main API Reference: QuicksilverClient to perform CRUD operations.
Developers requiring fine-grained control over API requests, or integrating with legacy systems, may choose to interact with these resources directly.
Manages direct interactions with the /accounts API endpoint for account creation, retrieval, listing, updating, and deletion.
Manages direct interactions with the /transactions API endpoint for transaction creation, retrieval, listing, updating, and deletion.
Manages direct interactions with the /streams API endpoint for streaming payment operations and real-time event subscriptions.
Provides administrative operations, typically requiring elevated privileges on the Quicksilver Engine.
Manages interactions with payment gateways.
Manages KYC (Know Your Customer) identity verification processes.
Provides methods for checking the health and status of the Quicksilver API.