A typical JOIN vault architecture is made of an ERC7540 and ERC4363. Depending on the customization, specials vaults can be deployed.
Supported Chains
This page lists all chains supported by JOIN Vaults API.
Chain
Chain ID
Status
Ethereum
1
Supported
Base
8453
Supported
Arbitrum
42161
Supported
Zksync
324
Supported
Solana
1151111081099710
Coming soon
🔑 API Keys
JOIN API authenticates your API requests using your account’s API key. Include your API key in the header of every request:x-join-key: <your_api_key>
Your API key carries many privileges, so be sure to keep it secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.
If your key is missing or invalid, the API will return 401 Unauthorized. You can always create or roll keys by contacting the JOIN team
🌐 Sandbox and Production Modes
All JOIN APIs are available in both Sandbox and Production environments. Use Sandbox for development and testing, then switch to Production when you’re ready to go live.
Sandbox
https://api.uat.private.getjoin.io
Use your sandbox API key. Integrate as you would in Production — the flow is identical. But actions are limited
