Authentication Errors
These errors occur when a request is not properly authenticated. Ensure that your API key orAuthorization header is correctly set.
| Error code | Description | Cause |
|---|---|---|
| 404 Not Found | Missing or invalid authorization | No Authorization header provided or invalid API token |
Client Request Errors
These errors result from issues in how the request was formed or processed. They are typically fixable by adjusting your query or payload.| Error code | Description | Cause |
|---|---|---|
| 400 Bad Request | Invalid request parameters | - Invalid JSON payload - Failed signature validation - Invalid query parameters such as minutes > 10- Duplicate signatures in consensus validation - Failed quorum check |
| 404 Not Found | Resource not found | - Invalid or missing feedIds parameter- No price data available for requested feeds - Empty results from data query |
| 500 Internal Server Error | Server processing error | - Failed to parse query parameters - Database/storage errors - Price conversion failures - Missing private key for wallet-signed endpoints - Internal processing errors |
| 204 No Content | Empty response | Single feed endpoint returns this when no data is available |
Troubleshooting
When working with oracles, you might encounter these common issues:Signature Verification Issues
- Ensure the recovery ID is correct (0 or 1).
- Verify that the message was hashed correctly, using the correct algorithm before signing.
- Check that the signature format matches exactly what was signed.
- Check that the signer’s public key is correctly registered.
Proof Verification Fails
- Verify that the proof format matches the expected schema.
- Check that all required fields are included.
- Ensure the proof hasn’t expired.
High Gas Costs or Gas Limit Issues
- Optimize proof size and complexity of proofs and transactions.
- Batch multiple updates or verifications into a single transaction where possible.
- Use gas-efficient proof schemes and push oracles for high-frequency updates.
- Consider using more gas-efficient proof schemes.
- Review and optimize your smart contract’s storage.
- Batch multiple verifications.
Stale Price Data
- Check your timestamp validation logic.
- Confirm your RPC node or validator is fully synced.
- Investigate potential network delays affecting update propagation.
Parameter Updates Not Taking Effect
- Ensure the parameter name is spelled exactly as expected.
- Confirm the update is applied to the correct signature or entity.
- Check that the update timestamp is recent enough to override existing values.