SecondaryDAO provides a REST API for programmatic access to real estate token trading on Arbitrum. Build trading bots, portfolio trackers, and custom integrations with HMAC-authenticated endpoints.
Browse properties and market data (public, no authentication required)
Track portfolio holdings, performance, and rental income
Place and manage buy/sell limit orders on the secondary market
Execute gasless token purchases during Initial Property Sales
Monitor rent distribution earnings and claim history
Check buyout offer status and requirements
Getting Started
-
Create an account at app.secondarydao.com and complete KYC verification
-
- Connect your wallet and pass AML screening
-
- Navigate to Profile > API Keys to generate your key and secret
-
- Authenticate requests using HMAC-SHA256 signed headers (your secret never leaves your machine)
How It Works
SecondaryDAO uses a hybrid architecture: orders are matched off-chain for speed (no gas fees), then settled on-chain via atomic token/stablecoin swaps. Your bot places orders via HTTP and the platform handles all blockchain execution. You do not sign individual trades.
Public endpoints like property listings and order books require no authentication. Authenticated endpoints use three headers: your API key ID, an HMAC-SHA256 signature, and a timestamp. The full documentation covers scopes, rate limits (300 req/min general, 30/min for orders), IP restrictions, and security best practices.
Full API Documentation
The complete API reference with endpoint details, code examples in Python and JavaScript, authentication guides, and the OpenAPI spec is available at:
https://secondarydao.github.io/api-docs/
Quick Start Guide: https://secondarydao.github.io/api-docs/guide.html
OpenAPI Specification: https://secondarydao.github.io/api-docs/openapi.yaml
Need Help?
If you run into issues with API authentication, rate limits, or endpoint behavior, check the error response body for specific error codes. Verify your API key is active, your clock is synchronized (timestamp must be within 30 seconds), and review the rate limit headers in the response. For additional support, reach out through the chat widget on this site.