API Validation Errors
Request validation failed: failed to get policy ID for address
Request validation failed: failed to get policy ID for address
Cause: The provided address doesn’t have an associated policy on the specified chainID.Solutions:
- Verify the
to
address has a policy configured in the Predicate dashboard - Ensure you’re using a supported chain ID
Missing required fields
Missing required fields
Cause: Request is missing mandatory transaction fields (Example Error:
from
, to
, data
, msg_value
).Solution: Include all required fields in your request:Missing required field: from
Unsupported chain ID
Unsupported chain ID
Cause: The specified chain ID is not supported by your configuration.Solutions:
- Use a supported chain ID (check your dashboard for available chains)
- Contact support to add chain support
- Verify chain configuration in your environment
unsupported chain ID 999
HTTP Status Errors
401 Unauthorized - Missing or invalid token
401 Unauthorized - Missing or invalid token
408 Request Timeout
408 Request Timeout
Cause: Transaction validation took longer than 25 seconds.Solutions:
- Retry the request with exponential backoff
- Contact support if timeouts persist
429 Rate Limited
429 Rate Limited
Cause: Too many requests in a short time period.Solutions:
- Implement exponential backoff in your retry logic
- Review your rate limits in the dashboard
- Consider upgrading your plan for higher limits (contact support)
Integration Errors
PredicateMessage verification failed
PredicateMessage verification failed
Cause: Attestation signature or format is incorrect for smart contract verification.Solutions:
- Validate signature encoding is correct (most likely culprit)
- Ensure you’re using the latest
PredicateClient.sol
- Verify the request to Predicate API matches the encoding on the application Contract