Skip to main content
GET
Get action by ID
Poll this after submitting a transaction until status is SUCCESS or FAILED; see Action statuses. transactions[] holds the current step only, each with its own status. Only actions created by your project are returned; anything else is 404.

Authorizations

x-api-key
string
header
required

Path Parameters

id
string
required

The unique identifier of the action (UUID)

Example:

"550e8400-e29b-41d4-a716-446655440000"

Response

Action details retrieved successfully

id
string
required

Unique action identifier (UUID)

Example:

"550e8400-e29b-41d4-a716-446655440000"

integrationId
string
required

Integration identifier

Example:

"aave-borrow"

action
enum<string>
required

Action type executed

Available options:
supply,
borrow,
repay,
withdraw,
enableCollateral,
disableCollateral,
supplyAndBorrow
Example:

"supply"

address
string
required

User wallet address

Example:

"0x742d35Cc6634C0532925a3b844Bc9e7595f8fB28"

status
enum<string>
required

Current action status

Available options:
CANCELED,
CREATED,
WAITING_FOR_NEXT,
PROCESSING,
FAILED,
SUCCESS,
STALE
Example:

"CREATED"

transactions
object[]
required

Transactions to sign (current step only)

hasNextStep
boolean
required

Whether there are more transactions to sign after the current step completes. When true, call POST /actions/:id/step after confirming to get the next transaction(s). Used for async multi-step flows such as cross-chain bridges or delayed withdrawals.

Example:

false

currentStep
number
required

Current step number (1-indexed)

Example:

1

totalSteps
number
required

Total number of steps in this action. Most actions are single-step. Multi-step actions occur when an async operation (e.g., bridge confirmation) must complete before the next transaction can be constructed.

Example:

1

createdAt
string<date-time>
required

When the action was created

rawArguments
object

Raw arguments as submitted

metadata
object

Action metadata with predicted position impact (health factor, LTV, USD totals)