pk_live_) for client-side calls and secret keys (sk_live_) for server-side calls. All action endpoints additionally require the user’s wallet to be registered as a Turtle member before any on-chain transaction can be generated.
Authentication
API key types, scopes, and how to pass them in requests.
Membership API
Register wallets as Turtle members to enable deposits and withdrawals.
API Keys
Publishable keys (pk_live_) are safe to use in client-side code. They provide read-only access to opportunities, deposit activity, and verification endpoints.
Secret keys (sk_live_) must be kept server-side. They are required for write operations such as generating deposit transactions, creating memberships, and managing streams.
Never expose your
sk_live_ key in client-side code, browser environments, or public repositories. Treat it like a database password.Wallet Membership
Before a wallet can interact with action endpoints, it must be registered as a Turtle member. Membership links a wallet address to a Turtle user, enabling deposit attribution and revenue tracking. Supported ecosystems:- EVM — Ethereum, Arbitrum, Base, and all supported EVM chains
- Solana
- TON