FAQsFrequently Asked Questions1. API error codesQ: What do the common HTTP status codes of the OpenOcean API mean?Q: How should I debug when I receive INVALID_PARAMS or similar errors?Q: What should I do if I get UNSUPPORTED_CHAIN or similar chain-not-supported errors?Q: How should I handle INSUFFICIENT_LIQUIDITY returned by the API?2. Common smart contract issues (swap / router / multicall)Q: When calling the OpenOcean router contract, the transaction reverts. What are the common reasons?Q: What are some typical on-chain transaction failure errors and their rough causes?Q: How do I debug a “revert caused by slippage”?Q: What are common pitfalls related to approve / token allowance?Q: What common issues arise when deploying across multiple chains?Q: How can I avoid insufficient gas estimation failures when calling the aggregator router?3. API application channels & onboardingQ: How can I apply for an OpenOcean API key?Q: What information is usually required when applying for an API key?Q: How should I securely manage the API key after it is issued?Q: Is it mandatory to apply for a key to use the OpenOcean API?4. API fees and rate limitsQ: Does OpenOcean charge for API usage?Q: What do OpenOcean API rate limits roughly look like?Q: What other fees are involved when trading via OpenOcean?Q: How can I confirm whether I am being charged any extra API usage fees?Next StepsQuick StartGet your first swap working in 5 minutes.
