Skip to main content
POST
Submit an on-chain transaction for fast relay. The relayer extracts any Hyperlane messages from the transaction, filters to eligible messages (currently CCTP V2 only), and immediately enqueues them for delivery — bypassing the normal block-polling delay.
Non-eligible messages (e.g. non-CCTP V2) are silently skipped. The response only contains messages that were accepted. An empty messages array means the transaction contained no eligible Hyperlane messages.
Hyperlane hosts public relay API endpoints:
  • Mainnet: https://relay-api.hyperlane.xyz/relay
  • Testnet: https://testnet-relay-api.hyperlane.xyz/relay
For self-hosted relayers, replace the URL with your relayer’s address (default: http://localhost:9090/relay).

Errors

Eligibility

Currently only CCTP V2 messages on EVM chains are eligible. A transaction qualifies when the number of MessageSent events from Circle’s MessageTransmitter V2 contract equals the number of Hyperlane Dispatch events. Messages that do not meet this criterion are silently omitted from the response rather than causing an error.

Deduplication

The relayer maintains a 5-minute deduplication window per (origin_chain, tx_hash) pair. Submitting the same transaction a second time within this window returns 429 Too Many Requests. After 5 minutes the same hash can be resubmitted. If the request fails with a non-2xx status the reservation is released immediately so the client can retry right away.

Health Check

A GET /relay request returns 200 OK with body up and can be used as a liveness probe.