Skip to main content
GET
Get Intent

Authorizations

x-api-key
string
header
required

Project API key.

Headers

x-api-version
enum<string>
required

API version. Required; pinned to this document.

Available options:
2026-09.caucasus

Path Parameters

id
string
required

Unique identifier of the intent operation

Pattern: ^\d+$
Example:

"77119256265773742309930654065362693497375232736834856992878277299604179621015"

Query Parameters

full
boolean

Whether to include intent operation details

Example:

true

Response

OK

Successfully retrieved intent operation status

intentId
string
required

Intent id — the one passed to GET /intents/:id

Example:

"12345678901234567890"

purpose
enum<string>
required

What the intent was for: execution moves funds or runs calls; deployment only initializes an account, and has no value.

Available options:
execution,
deployment
Example:

"execution"

status
enum<string>
required

Overall intent status: PENDING, COMPLETED, or FAILED

Available options:
PENDING,
COMPLETED,
FAILED
Example:

"COMPLETED"

operations
object[]
required

Operations grouped by chain

refunds
object[]
required

Bridge refunds observed for this intent — a settlement layer returned the funds to the account instead of delivering them. Not operations: Rhinestone neither built nor broadcast these transactions, and a refund never makes the intent succeed. Empty means none were observed, which is every delivered intent and also a failed one whose refund we have not (or not yet) seen — so an empty list is not evidence that funds were kept.

accounts
object[]

The accounts this intent acts through, one entry per chain it acts on — each origin chain, then the destination. Projected from the resolved plan, so it names an account exactly as the quote did. Absent when the record carries no account context; a HyperCore delivery carries its origins only where the record cannot supply the venue it addressed.

details
object

Extended intent details, returned only when full=true