# API Reference \[Stridge REST API] The Stridge REST API powers multi-chain **Wallet-as-a-Service**, real-time **deposit detection**, **treasury transfers**, **vault management**, **gas-station routing**, and **network lookups** across TRON, Ethereum, BSC, Polygon, Base, and more. Every endpoint is authenticated with your API key. ## Base URL ```text https://api.stridge.com/v1 ``` Use `https://api.stridge.dev/v1` for the sandbox environment. ## Authentication All requests must include your API key in the `X-API-Key` header. ```bash curl -X GET 'https://api.stridge.com/v1/wallets' \ -H 'X-API-Key: your_api_key_here' ``` Generate keys in the [Stridge Dashboard](https://beta.dashboard.stridge.com). Keep them server-side — they grant full account access. ## Endpoints ## Response format Successful responses follow a consistent envelope: ```json { "success": true, "message": "operation completed successfully", "data": { /* endpoint-specific payload */ } } ``` Errors use the same envelope with a machine-readable code: ```json { "success": false, "code": 400, "error": "invalid request" } ``` ## Rate limits API requests are rate-limited to protect platform stability: | Tier | Requests / minute | | ------------ | ----------------- | | Standard | 100 | | Pro | 1,000 | | Enterprise | Custom | Every response includes `X-RateLimit-Limit`, `X-RateLimit-Remaining`, and `X-RateLimit-Reset` headers. A `429 Too Many Requests` indicates you've exceeded your limit — we recommend exponential backoff. ## Need help?