Server-side SDKs for the hosted Swig wallet API. The Swig API prepares wallet transactions; your application signs and submits them.
Canonical source: https://github.com/anagrambuild/swig-developer-sdk
| Package | Language | Version | Directory |
|---|---|---|---|
@swig-wallet/developer-sdk |
TypeScript | 0.9.0 |
typescript |
swig-developer-sdk |
Python | 0.8.0 |
python |
Both packages target the public API base URL https://api.onswig.com.
- Your server creates a client with an API key.
- Your server prepares a wallet operation and receives one or more unsigned transactions.
- Your application obtains every required signature outside the server SDK.
- Your app submits them directly, or through Swig's paymaster sponsorship.
API keys stay on the server. Send prepared transactions to your application-owned signer, then return the signed transactions to the server for sponsorship or submission.
TypeScript signs with @solana/web3.js; Python signs with solders. Neither
package sends signing material to the API.
# TypeScript
bun add @swig-wallet/developer-sdk
# Python
pip install swig-developer-sdkCreate an API key in the Swig dashboard.
typescript/ @swig-wallet/developer-sdk sources and tests
python/ swig-developer-sdk sources and tests
Apache-2.0. See LICENSE.txt.