This documentation is restricted to authorised members of the SWSS Developer Community. Access is granted exclusively through SWSS DevHub, after KYB and SWSS Foundation approval.
All SwssChain GitHub repositories are private. Significant updates are currently deploying across the full SWSS Ecosystem. SDK and API specifications are subject to change at any time in accordance with security requirements and SwssChain Foundation governance decisions.
SWSS SDK v2.1 is deploying across the ecosystem. API signatures may change during this period. Ensure your integration uses the latest schema from SWSS DevHub.
Where do I get an API key?
From the SWSS DevHub dashboard, after your developer application has completed KYB and been approved. See Developer and Validator Access.
I lost my key. Can it be shown again?
No. A key is displayed in full once at generation. Generate a new one and revoke the old.
Can I pass the key as a query parameter?
It is accepted for quick testing but should not be used in production, where URLs are frequently logged by proxies, load balancers and error trackers. Use the X-API-Key header.
What is the difference between 401 and 403?
401 means the key is missing or invalid. 403 means the key is valid but does not carry permission for that endpoint: usually a tier your approval does not cover.
How do I report a failing request?
Every error response carries a requestId. Quote it to SWSS DevHub support; it identifies the exact request without you having to reproduce it.
Is one key enough for mainnet and testnet?
A key is scoped at generation. Generate separately for each network unless you selected both, and prefer separate keys regardless so usage is attributable per environment.
