CCIP API
REST API for querying cross-chain message data, lane information, and intent operations on the Chainlink Cross-Chain Interoperability Protocol.
Multi-Chain Support
The CCIP API supports querying messages and lanes across multiple blockchain ecosystems:
Supported chain families:
EVM
Solana
Aptos
EVMSolanaAptosQuick Reference
| Use Case | Endpoint | Action |
|---|---|---|
| Track a cross-chain message | Retrieve a Message | Try it live → |
| Check lane performance | Get Lane Latency | Try it live → |
| Get a quote for intent transfer | Get Intent Quote | Try it live → |
| Find intents by transaction | Get Intents by Tx Hash | Try it live → |
| Track intent status | Get Intent by ID | Try it live → |
Each endpoint page includes:
- Full request/response schema
- Code samples in 9 languages
- Interactive playground to test live
HTTP Status Codes
All endpoints return standardized HTTP status codes:
| Code | Meaning |
|---|---|
200 | Success - request completed successfully |
400 | Bad Request - invalid parameters or malformed request |
404 | Not Found - resource does not exist (message ID, intent ID) |
500 | Server Error - internal error, retry with exponential backoff |
Bash
# Example: Check response status in scripts
curl -s -o /dev/null -w "%{http_code}" \
"https://api.ccip.chain.link/v2/message/0x..."
Authentication
The CCIP API is publicly accessible and does not require authentication. However, please be mindful of rate limits when integrating into production applications.
Best Practices
- Cache responses - Message data is immutable once finalized
- Use pagination - For endpoints returning lists, use limit/offset parameters
- Handle retries - Implement exponential backoff for 5xx errors
- Validate inputs - Message IDs must be 66-character hex strings (
0x+ 64 hex chars)
Next Steps
- Retrieve a Message - Track your first cross-chain message
- Get Lane Latency - Check lane performance metrics
- Get Intent Quote - Get pricing for intent-based transfers