Submit transaction

Transaction · Acts onchain

Relays or arms a signed program created on the same path. The signature must come from the owning wallet, which makes this the one surface in the API that cannot act on an arbitrary address. Everything before it, reading, composing, compiling, is open; the moment value can move, the wallet is the gate. The program must match one the create step stored. In `manual` mode it is relayed at once, the relayer paying the gas and deploying the Plug Account if it has no code yet, and the response carries the `transaction_hash` and the `intent_id` it fired. In `scheduled` mode the stored intent is armed and returned as the same row the transactions list carries, and it fires when its conditions are met. Reach for it as the final step of the flow the create and compile surfaces set up: sign what they produced, hand it over, and track the record through the transactions list.

Send a request

Request body

{
chain_id: number
mode: string
owner: string
salt: string | undefined
plugs: string[]
state: string[]
signature: string
}

Response

{
transaction_hash: string
intent_id: string
}

Code samples

Language

Claude

Prompt

Call the Plug API endpoint "Submit transaction".
## Endpoint
PUT /address/{address}/transaction/
Base URL: https://api.plug.to
## Description
Relays or arms a signed program created on the same path.
The signature must come from the owning wallet, which makes this the one surface in the API that cannot act on an arbitrary address. Everything before it, reading, composing, compiling, is open; the moment value can move, the wallet is the gate. The program must match one the create step stored. In `manual` mode it is relayed at once, the relayer paying the gas and deploying the Plug Account if it has no code yet, and the response carries the `transaction_hash` and the `intent_id` it fired. In `scheduled` mode the stored intent is armed and returned as the same row the transactions list carries, and it fires when its conditions are met.
Reach for it as the final step of the flow the create and compile surfaces set up: sign what they produced, hand it over, and track the record through the transactions list.
## Path Parameters
- address (string, required) — The EVM address to get information for. In the case that you request an address we have never indexed, we will immediately index it.
Current value: 0x62180042606624f02d8a130da8a3171e9b33894d
## Request Body
- chain_id (integer, required)
- mode (string, required)
- owner (string, required)
- salt (string, optional)
- plugs (array of string, required)
- state (array of string, required)
- signature (string, required)
## Response Schema
- transaction_hash (string, required)
- intent_id (string, required)
## Example Request
PUT https://api.plug.to/address/0x62180042606624f02d8a130da8a3171e9b33894d/transaction/