Skip to main content
POST
DEPRECATED for new integrations; behaviorally stable for existing ones.
Deprecated for new integrations. CommitIntent remains behaviorally stable for existing callers, but new integrations should call ExecuteIntent directly on a QUOTED intent. For a Solana or Tron origin, arm fill monitoring with ExecuteIntentEdge instead.

Overview

The CommitIntent endpoint validates a quoted intent, atomically arms origin edge quotes, and transitions the intent from QUOTED to COMMITTED. New clients skip this step — ExecuteIntent accepts QUOTED intents directly and folds in the same validation.

Use Cases

  • Legacy integrations that still separate the commit step from execution
  • Preserving compatibility with older SDKs that call CommitIntent before ExecuteIntent

Request Parameters

Required Fields

  • intent (Intent): The complete intent object returned from QuoteIntent

Response

The response includes:
  • intentId (string): Unique identifier for the committed intent

Intent Lifecycle

Legacy flow (existing callers):
Current flow (new integrations):
For Solana/Tron origins, replace ExecuteIntent with ExecuteIntentEdge to arm fill monitoring before the user pays on the edge chain.

Example

Important Notes

Committed intents share the quote’s expiry — call ExecuteIntent within 15 minutes of the original QuoteIntent call. CommitIntent does not extend the window; if the quote expires, request a fresh one.
The intent object from QuoteIntent must be forwarded unmodified — the server rejects mutated intents.

Next Steps

After committing an intent:
  1. Prepare the transaction signature using the provided intent details for the user to deposit into the intent address.
  2. Execute the transaction with ExecuteIntent.
  3. Monitor the transaction status with WaitIntentReceipt.

Body

application/json
intent
object
required

Response

OK

intentId
string
required