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-04.blanc

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

status
enum<string>
required

Overall intent status: PENDING, COMPLETED, or FAILED

Available options:
PENDING,
COMPLETED,
FAILED
Example:

"COMPLETED"

accountAddress
string
required

Account address

Example:

"0x3672e268a79bd4acc5ee646bdda652547c7a435c"

operations
object[]
required

Operations grouped by chain. Each chain has one or more operations (e.g. CLAIM, FILL, BRIDGE_FILL).

refunds
object[]

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. Omitted when none are known, which is every delivered intent and also a failed one whose refund we have not (or not yet) observed — so its absence is not evidence that funds were kept.

hyperCore
object

What Hyperliquid did with this intent's options.hyperCore action, and the only record of it — the action is the one leg of an intent that is not a transaction. Omitted for every intent that carried none.

It DECIDES status rather than annotating it: an intent whose action was refused reports FAILED even though every operation completed, because the delivery landed and the trade did not. The funds are in the account's own HyperCore balance either way, so a refusal is recoverable by trading again — it is not a loss.

details
object

Extended intent details, returned only when full=true