Submit batch transactions

POST

/transactions/batch

Test request

CURL *hnd = curl_easy_init();

curl_easy_setopt(hnd, CURLOPT_CUSTOMREQUEST, "POST");
curl_easy_setopt(hnd, CURLOPT_URL, "https://api.mainnet.aptoslabs.com/v1/transactions/batch");

CURLcode ret = curl_easy_perform(hnd);

using System.Net.Http.Headers;
var client = new HttpClient();
var request = new HttpRequestMessage
{
    Method = HttpMethod.Post,
    RequestUri = new Uri("https://api.mainnet.aptoslabs.com/v1/transactions/batch"),
};
using (var response = await client.SendAsync(request))
{
    response.EnsureSuccessStatusCode();
    var body = await response.Content.ReadAsStringAsync();
    Console.WriteLine(body);
}

var client = new RestClient("https://api.mainnet.aptoslabs.com/v1/transactions/batch");
var request = new RestRequest(Method.POST);
IRestResponse response = client.Execute(request);

(require '[clj-http.client :as client])

(client/post "https://api.mainnet.aptoslabs.com/v1/transactions/batch")

import 'package:http/http.dart' as http;

void main() async {
  final response = await http.post(Uri.parse('https://api.mainnet.aptoslabs.com/v1/transactions/batch'));
  print(response.body);
}

package main

import (
  "fmt"
  "io"
  "net/http"
)

func main() {
  url := "https://api.mainnet.aptoslabs.com/v1/transactions/batch"

  req, _ := http.NewRequest("POST", url, nil)

  res, _ := http.DefaultClient.Do(req)

  defer res.Body.Close()
  body, _ := io.ReadAll(res.Body)

  fmt.Println(res)
  fmt.Println(string(body))

}

POST /v1/transactions/batch HTTP/1.1
Host: api.mainnet.aptoslabs.com

AsyncHttpClient client = new DefaultAsyncHttpClient();
client.prepare("POST", "https://api.mainnet.aptoslabs.com/v1/transactions/batch")
  .execute()
  .toCompletableFuture()
  .thenAccept(System.out::println)
  .join();

client.close();

HttpRequest request = HttpRequest.newBuilder()
    .uri(URI.create("https://api.mainnet.aptoslabs.com/v1/transactions/batch"))
    .method("POST", HttpRequest.BodyPublishers.noBody())
    .build();
HttpResponse<String> response = HttpClient.newHttpClient().send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());

OkHttpClient client = new OkHttpClient();

Request request = new Request.Builder()
  .url("https://api.mainnet.aptoslabs.com/v1/transactions/batch")
  .post(null)
  .build();

Response response = client.newCall(request).execute();

HttpResponse<String> response = Unirest.post("https://api.mainnet.aptoslabs.com/v1/transactions/batch")
  .asString();

fetch('https://api.mainnet.aptoslabs.com/v1/transactions/batch', {
  method: 'POST'
})

import axios from 'axios';

const options = {method: 'POST', url: 'https://api.mainnet.aptoslabs.com/v1/transactions/batch'};

try {
  const { data } = await axios.request(options);
  console.log(data);
} catch (error) {
  console.error(error);
}

import { ofetch } from 'ofetch'

ofetch('https://api.mainnet.aptoslabs.com/v1/transactions/batch', {
  method: 'POST'
})

const settings = {
  async: true,
  crossDomain: true,
  url: 'https://api.mainnet.aptoslabs.com/v1/transactions/batch',
  method: 'POST',
  headers: {}
};

$.ajax(settings).done(function (response) {
  console.log(response);
});

const data = null;

const xhr = new XMLHttpRequest();
xhr.withCredentials = true;

xhr.addEventListener('readystatechange', function () {
  if (this.readyState === this.DONE) {
    console.log(this.responseText);
  }
});

xhr.open('POST', 'https://api.mainnet.aptoslabs.com/v1/transactions/batch');

xhr.send(data);

val client = OkHttpClient()

val request = Request.Builder()
  .url("https://api.mainnet.aptoslabs.com/v1/transactions/batch")
  .post(null)
  .build()

val response = client.newCall(request).execute()

fetch('https://api.mainnet.aptoslabs.com/v1/transactions/batch', {
  method: 'POST'
})

const axios = require('axios').default;

const options = {method: 'POST', url: 'https://api.mainnet.aptoslabs.com/v1/transactions/batch'};

try {
  const { data } = await axios.request(options);
  console.log(data);
} catch (error) {
  console.error(error);
}

import { ofetch } from 'ofetch'

ofetch('https://api.mainnet.aptoslabs.com/v1/transactions/batch', {
  method: 'POST'
})

import { request } from 'undici'

const { statusCode, body } = await request('https://api.mainnet.aptoslabs.com/v1/transactions/batch', {
  method: 'POST'
})

#import <Foundation/Foundation.h>

NSMutableURLRequest *request = [NSMutableURLRequest requestWithURL:[NSURL URLWithString:@"https://api.mainnet.aptoslabs.com/v1/transactions/batch"]
                                                       cachePolicy:NSURLRequestUseProtocolCachePolicy
                                                   timeoutInterval:10.0];
[request setHTTPMethod:@"POST"];

NSURLSession *session = [NSURLSession sharedSession];
NSURLSessionDataTask *dataTask = [session dataTaskWithRequest:request
                                            completionHandler:^(NSData *data, NSURLResponse *response, NSError *error) {
                                                if (error) {
                                                    NSLog(@"%@", error);
                                                } else {
                                                    NSHTTPURLResponse *httpResponse = (NSHTTPURLResponse *) response;
                                                    NSLog(@"%@", httpResponse);
                                                }
                                            }];
[dataTask resume];

open Cohttp_lwt_unix
open Cohttp
open Lwt

let uri = Uri.of_string "https://api.mainnet.aptoslabs.com/v1/transactions/batch" in

Client.call `POST uri
>>= fun (res, body_stream) ->
  (* Do stuff with the result *)

$ch = curl_init("https://api.mainnet.aptoslabs.com/v1/transactions/batch");

curl_setopt($ch, CURLOPT_POST, true);

curl_exec($ch);

curl_close($ch);

$client = new GuzzleHttp\Client();

$response = $client->request('POST', 'https://api.mainnet.aptoslabs.com/v1/transactions/batch');

$response = Invoke-WebRequest -Uri 'https://api.mainnet.aptoslabs.com/v1/transactions/batch' -Method POST

$response = Invoke-RestMethod -Uri 'https://api.mainnet.aptoslabs.com/v1/transactions/batch' -Method POST

import http.client

conn = http.client.HTTPSConnection("api.mainnet.aptoslabs.com")

conn.request("POST", "/v1/transactions/batch")

res = conn.getresponse()
data = res.read()

print(data.decode("utf-8"))

requests.post(
    "https://api.mainnet.aptoslabs.com/v1/transactions/batch"
)

httpx.post(
    "https://api.mainnet.aptoslabs.com/v1/transactions/batch"
)

with httpx.AsyncClient() as client:
    await client.post(
        "https://api.mainnet.aptoslabs.com/v1/transactions/batch"
    )

library(httr)

url <- "https://api.mainnet.aptoslabs.com/v1/transactions/batch"

response <- VERB("POST", url, content_type("application/octet-stream"))

content(response, "text")

require 'uri'
require 'net/http'

url = URI("https://api.mainnet.aptoslabs.com/v1/transactions/batch")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Post.new(url)

response = http.request(request)
puts response.read_body

let client = reqwest::Client::new();

let request = client.post("https://api.mainnet.aptoslabs.com/v1/transactions/batch");

let response = request.send().await?;

curl https://api.mainnet.aptoslabs.com/v1/transactions/batch \
  --request POST

wget --quiet \
  --method POST \
  --output-document \
  - https://api.mainnet.aptoslabs.com/v1/transactions/batch

http POST https://api.mainnet.aptoslabs.com/v1/transactions/batch

import Foundation

let request = NSMutableURLRequest(url: NSURL(string: "https://api.mainnet.aptoslabs.com/v1/transactions/batch")! as URL,
                                        cachePolicy: .useProtocolCachePolicy,
                                    timeoutInterval: 10.0)
request.httpMethod = "POST"

let session = URLSession.shared
let dataTask = session.dataTask(with: request as URLRequest, completionHandler: { (data, response, error) -> Void in
  if (error != nil) {
    print(error as Any)
  } else {
    let httpResponse = response as? HTTPURLResponse
    print(httpResponse)
  }
})

dataTask.resume()

This allows you to submit multiple transactions. The response has three outcomes:

1. All transactions succeed, and it will return a 202
2. Some transactions succeed, and it will return the failed transactions and a 206
3. No transactions succeed, and it will also return the failed transactions and a 206

To submit a transaction as JSON, you must submit a SubmitTransactionRequest. To build this request, do the following:

1. Encode the transaction as BCS. If you are using a language that has native BCS support, make sure to use that library. If not, you may take advantage of /transactions/encode_submission. When using this endpoint, make sure you trust the node you’re talking to, as it is possible they could manipulate your request.
2. Sign the encoded transaction and use it to create a TransactionSignature.
3. Submit the request. Make sure to use the “application/json” Content-Type.

To submit a transaction as BCS, you must submit a SignedTransaction encoded as BCS. See SignedTransaction in types/src/transaction/mod.rs. Make sure to use the application/x.aptos.signed_transaction+bcs Content-Type.

Request Body ^required

Array<object>

A request to submit a transaction

This requires a transaction and a signature of it

object

sender

required

A hex encoded 32 byte Aptos account address.

This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.

For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

sequence_number

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

string format: uint64

32425224034

max_gas_amount

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

string format: uint64

32425224034

gas_unit_price

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

string format: uint64

32425224034

expiration_timestamp_secs

required

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

string format: uint64

32425224034

payload

required

One of: discriminator: type

object

An enum of the possible transaction payloads

object

type

required

string

Allowed values: entry_function_payload

entry_function_payload

function

required

Entry function id is string representation of a entry function defined on-chain.

Format: {address}::{module name}::{function name}

Both module name and function name are case-sensitive.

string

0x1::aptos_coin::transfer

type_arguments

required

Type arguments of the function

Array<string>

arguments

required

Arguments of the function

Array

object

An enum of the possible transaction payloads

object

type

required

string

Allowed values: script_payload

script_payload

code

required

Move script bytecode

object

bytecode

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

abi

Move function

object

name

required

string

visibility

required

Move function visibility

string

Allowed values: private public friend

is_entry

required

Whether the function can be called as an entry function directly in a transaction

boolean

is_view

required

Whether the function is a view function or not

boolean

generic_type_params

required

Generic type params associated with the Move function

Array<object>

Move function generic type param

object

constraints

required

Move abilities tied to the generic type param and associated with the function that uses it

Array<string>

params

required

Parameters associated with the move function

Array<string>

return

required

Return type of the function

Array<string>

type_arguments

required

Type arguments of the function

Array<string>

arguments

required

Arguments of the function

Array

object

An enum of the possible transaction payloads

object

type

required

string

Allowed values: module_bundle_payload

module_bundle_payload

object

An enum of the possible transaction payloads

object

type

required

string

Allowed values: multisig_payload

multisig_payload

multisig_address

required

A hex encoded 32 byte Aptos account address.

This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.

For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

transaction_payload

One of: discriminator: type

object

object

type

required

string

Allowed values: entry_function_payload

entry_function_payload

function

required

Entry function id is string representation of a entry function defined on-chain.

Format: {address}::{module name}::{function name}

Both module name and function name are case-sensitive.

string

0x1::aptos_coin::transfer

type_arguments

required

Type arguments of the function

Array<string>

arguments

required

Arguments of the function

Array

replay_protection_nonce

A string containing a 64-bit unsigned integer.

We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.

string format: uint64

32425224034

signature

required

One of: discriminator: type

object

An enum representing the different transaction signatures available

object

type

required

string

Allowed values: ed25519_signature

ed25519_signature

public_key

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signature

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

An enum representing the different transaction signatures available

object

type

required

string

Allowed values: multi_ed25519_signature

multi_ed25519_signature

public_keys

required

The public keys for the Ed25519 signature

Array<string>

signatures

required

Signature associated with the public keys in the same order

Array<string>

threshold

required

The number of signatures required for a successful transaction

integer format: uint8

bitmap

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

An enum representing the different transaction signatures available

object

type

required

string

Allowed values: multi_agent_signature

multi_agent_signature

sender

required

One of: discriminator: type

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: ed25519_signature

ed25519_signature

public_key

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signature

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: multi_ed25519_signature

multi_ed25519_signature

public_keys

required

The public keys for the Ed25519 signature

Array<string>

signatures

required

Signature associated with the public keys in the same order

Array<string>

threshold

required

The number of signatures required for a successful transaction

integer format: uint8

bitmap

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: single_key_signature

single_key_signature

public_key

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256r1_ecdsa

secp256r1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: federated_keyless

federated_keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signature

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: web_authn

web_authn

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: multi_key_signature

multi_key_signature

public_keys

required

Array<object>

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256r1_ecdsa

secp256r1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: federated_keyless

federated_keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signatures

required

Array<object>

object

index

required

integer format: uint8

signature

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: web_authn

web_authn

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signatures_required

required

integer format: uint8

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: no_account_signature

no_account_signature

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: abstraction_signature

abstraction_signature

function_info

required

string

auth_data

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

secondary_signer_addresses

required

The other involved parties’ addresses

Array<string>

secondary_signers

required

The associated signatures, in the same order as the secondary addresses

Array<object>

One of: discriminator: type

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: ed25519_signature

ed25519_signature

public_key

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signature

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: multi_ed25519_signature

multi_ed25519_signature

public_keys

required

The public keys for the Ed25519 signature

Array<string>

signatures

required

Signature associated with the public keys in the same order

Array<string>

threshold

required

The number of signatures required for a successful transaction

integer format: uint8

bitmap

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: single_key_signature

single_key_signature

public_key

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256r1_ecdsa

secp256r1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: federated_keyless

federated_keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signature

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: web_authn

web_authn

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: multi_key_signature

multi_key_signature

public_keys

required

Array<object>

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256r1_ecdsa

secp256r1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: federated_keyless

federated_keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signatures

required

Array<object>

object

index

required

integer format: uint8

signature

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: web_authn

web_authn

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signatures_required

required

integer format: uint8

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: no_account_signature

no_account_signature

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: abstraction_signature

abstraction_signature

function_info

required

string

auth_data

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

An enum representing the different transaction signatures available

object

type

required

string

Allowed values: fee_payer_signature

fee_payer_signature

sender

required

One of: discriminator: type

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: ed25519_signature

ed25519_signature

public_key

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signature

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: multi_ed25519_signature

multi_ed25519_signature

public_keys

required

The public keys for the Ed25519 signature

Array<string>

signatures

required

Signature associated with the public keys in the same order

Array<string>

threshold

required

The number of signatures required for a successful transaction

integer format: uint8

bitmap

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: single_key_signature

single_key_signature

public_key

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256r1_ecdsa

secp256r1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: federated_keyless

federated_keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signature

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: web_authn

web_authn

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: multi_key_signature

multi_key_signature

public_keys

required

Array<object>

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256r1_ecdsa

secp256r1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: federated_keyless

federated_keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signatures

required

Array<object>

object

index

required

integer format: uint8

signature

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: web_authn

web_authn

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signatures_required

required

integer format: uint8

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: no_account_signature

no_account_signature

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: abstraction_signature

abstraction_signature

function_info

required

string

auth_data

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

secondary_signer_addresses

required

The other involved parties’ addresses

Array<string>

secondary_signers

required

The associated signatures, in the same order as the secondary addresses

Array<object>

One of: discriminator: type

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: ed25519_signature

ed25519_signature

public_key

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signature

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: multi_ed25519_signature

multi_ed25519_signature

public_keys

required

The public keys for the Ed25519 signature

Array<string>

signatures

required

Signature associated with the public keys in the same order

Array<string>

threshold

required

The number of signatures required for a successful transaction

integer format: uint8

bitmap

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: single_key_signature

single_key_signature

public_key

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256r1_ecdsa

secp256r1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: federated_keyless

federated_keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signature

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: web_authn

web_authn

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: multi_key_signature

multi_key_signature

public_keys

required

Array<object>

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256r1_ecdsa

secp256r1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: federated_keyless

federated_keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signatures

required

Array<object>

object

index

required

integer format: uint8

signature

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: web_authn

web_authn

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signatures_required

required

integer format: uint8

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: no_account_signature

no_account_signature

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: abstraction_signature

abstraction_signature

function_info

required

string

auth_data

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

fee_payer_address

required

string format: hex

fee_payer_signer

required

object

One of:

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: ed25519_signature

ed25519_signature

public_key

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signature

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: multi_ed25519_signature

multi_ed25519_signature

public_keys

required

The public keys for the Ed25519 signature

Array<string>

signatures

required

Signature associated with the public keys in the same order

Array<string>

threshold

required

The number of signatures required for a successful transaction

integer format: uint8

bitmap

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: single_key_signature

single_key_signature

public_key

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256r1_ecdsa

secp256r1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: federated_keyless

federated_keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signature

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: web_authn

web_authn

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: multi_key_signature

multi_key_signature

public_keys

required

Array<object>

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256r1_ecdsa

secp256r1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: federated_keyless

federated_keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signatures

required

Array<object>

object

index

required

integer format: uint8

signature

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: web_authn

web_authn

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signatures_required

required

integer format: uint8

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: no_account_signature

no_account_signature

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: abstraction_signature

abstraction_signature

function_info

required

string

auth_data

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

An enum representing the different transaction signatures available

object

type

required

string

Allowed values: single_sender

single_sender

One of: discriminator: type

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: ed25519_signature

ed25519_signature

public_key

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signature

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: multi_ed25519_signature

multi_ed25519_signature

public_keys

required

The public keys for the Ed25519 signature

Array<string>

signatures

required

Signature associated with the public keys in the same order

Array<string>

threshold

required

The number of signatures required for a successful transaction

integer format: uint8

bitmap

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: single_key_signature

single_key_signature

public_key

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256r1_ecdsa

secp256r1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: federated_keyless

federated_keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signature

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: web_authn

web_authn

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: multi_key_signature

multi_key_signature

public_keys

required

Array<object>

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256r1_ecdsa

secp256r1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: federated_keyless

federated_keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signatures

required

Array<object>

object

index

required

integer format: uint8

signature

required

One of: discriminator: type

object

object

type

required

string

Allowed values: ed25519

ed25519

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: secp256k1_ecdsa

secp256k1_ecdsa

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: web_authn

web_authn

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

object

type

required

string

Allowed values: keyless

keyless

value

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

signatures_required

required

integer format: uint8

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: no_account_signature

no_account_signature

object

Account signature scheme

The account signature scheme allows you to have two types of accounts:

1. A single Ed25519 key account, one private key
2. A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
3. A single Secp256k1Ecdsa key account, one private key

object

type

required

string

Allowed values: abstraction_signature

abstraction_signature

function_info

required

string

auth_data

required

All bytes (Vec) data is represented as hex-encoded string prefixed with 0x and fulfilled with two hex digits per byte.

Unlike the Address type, HexEncodedBytes will not trim any zeros.

string format: hex

0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1

object

An enum representing the different transaction signatures available

object

type

required

string

Allowed values: no_account_signature

no_account_signature

Array<integer>

Responses

202

Batch transaction submission result

Tells which transactions failed

object

transaction_failures

required

Summary of the failed transactions

Array<object>

Information telling which batch submission transactions failed

object

error

required

This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.

object

message

required

A message describing the error

string

error_code

required

These codes provide more granular error information beyond just the HTTP status code of the response.

string

Allowed values: account_not_found resource_not_found module_not_found struct_field_not_found version_not_found transaction_not_found table_item_not_found block_not_found state_value_not_found version_pruned block_pruned invalid_input invalid_transaction_update sequence_number_too_old vm_error rejected_by_filter health_check_failed mempool_is_full internal_error web_framework_error bcs_not_supported api_disabled

vm_error_code

A code providing VM error details when submitting transactions to the VM

integer format: uint64

transaction_index

required

The index of which transaction failed, same as submission order

integer format: uint64

Array<integer>

Headers

X-APTOS-CHAIN-ID

required

integer format: uint8

Chain ID of the current chain

X-APTOS-LEDGER-VERSION

required

integer format: uint64

Current ledger version of the chain

X-APTOS-LEDGER-OLDEST-VERSION

required

integer format: uint64

Oldest non-pruned ledger version of the chain

X-APTOS-LEDGER-TIMESTAMPUSEC

required

integer format: uint64

Current timestamp of the chain

X-APTOS-EPOCH

required

integer format: uint64

Current epoch of the chain

X-APTOS-BLOCK-HEIGHT

required

integer format: uint64

Current block height of the chain

X-APTOS-OLDEST-BLOCK-HEIGHT

required

integer format: uint64

Oldest non-pruned block height of the chain

X-APTOS-GAS-USED

integer format: uint64

The cost of the call in terms of gas

X-APTOS-CURSOR

string

Cursor to be used for endpoints that support cursor-based pagination. Pass this to the start field of the endpoint on the next call to get the next page of results.

206

Batch transaction submission result

Tells which transactions failed

object

transaction_failures

required

Summary of the failed transactions

Array<object>

Information telling which batch submission transactions failed

object

error

required

This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.

object

message

required

A message describing the error

string

error_code

required

These codes provide more granular error information beyond just the HTTP status code of the response.

string

Allowed values: account_not_found resource_not_found module_not_found struct_field_not_found version_not_found transaction_not_found table_item_not_found block_not_found state_value_not_found version_pruned block_pruned invalid_input invalid_transaction_update sequence_number_too_old vm_error rejected_by_filter health_check_failed mempool_is_full internal_error web_framework_error bcs_not_supported api_disabled

vm_error_code

A code providing VM error details when submitting transactions to the VM

integer format: uint64

transaction_index

required

The index of which transaction failed, same as submission order

integer format: uint64

Array<integer>

Headers

X-APTOS-CHAIN-ID

required

integer format: uint8

Chain ID of the current chain

X-APTOS-LEDGER-VERSION

required

integer format: uint64

Current ledger version of the chain

X-APTOS-LEDGER-OLDEST-VERSION

required

integer format: uint64

Oldest non-pruned ledger version of the chain

X-APTOS-LEDGER-TIMESTAMPUSEC

required

integer format: uint64

Current timestamp of the chain

X-APTOS-EPOCH

required

integer format: uint64

Current epoch of the chain

X-APTOS-BLOCK-HEIGHT

required

integer format: uint64

Current block height of the chain

X-APTOS-OLDEST-BLOCK-HEIGHT

required

integer format: uint64

Oldest non-pruned block height of the chain

X-APTOS-GAS-USED

integer format: uint64

The cost of the call in terms of gas

X-APTOS-CURSOR

string

Cursor to be used for endpoints that support cursor-based pagination. Pass this to the start field of the endpoint on the next call to get the next page of results.

400

application/json

This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.

object

message

required

A message describing the error

string

error_code

required

These codes provide more granular error information beyond just the HTTP status code of the response.

string

Allowed values: account_not_found resource_not_found module_not_found struct_field_not_found version_not_found transaction_not_found table_item_not_found block_not_found state_value_not_found version_pruned block_pruned invalid_input invalid_transaction_update sequence_number_too_old vm_error rejected_by_filter health_check_failed mempool_is_full internal_error web_framework_error bcs_not_supported api_disabled

vm_error_code

A code providing VM error details when submitting transactions to the VM

integer format: uint64

Headers

X-APTOS-CHAIN-ID

integer format: uint8

Chain ID of the current chain

X-APTOS-LEDGER-VERSION

integer format: uint64

Current ledger version of the chain

X-APTOS-LEDGER-OLDEST-VERSION

integer format: uint64

Oldest non-pruned ledger version of the chain

X-APTOS-LEDGER-TIMESTAMPUSEC

integer format: uint64

Current timestamp of the chain

X-APTOS-EPOCH

integer format: uint64

Current epoch of the chain

X-APTOS-BLOCK-HEIGHT

integer format: uint64

Current block height of the chain

X-APTOS-OLDEST-BLOCK-HEIGHT

integer format: uint64

Oldest non-pruned block height of the chain

X-APTOS-GAS-USED

integer format: uint64

The cost of the call in terms of gas

403

application/json

This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.

object

message

required

A message describing the error

string

error_code

required

These codes provide more granular error information beyond just the HTTP status code of the response.

string

Allowed values: account_not_found resource_not_found module_not_found struct_field_not_found version_not_found transaction_not_found table_item_not_found block_not_found state_value_not_found version_pruned block_pruned invalid_input invalid_transaction_update sequence_number_too_old vm_error rejected_by_filter health_check_failed mempool_is_full internal_error web_framework_error bcs_not_supported api_disabled

vm_error_code

A code providing VM error details when submitting transactions to the VM

integer format: uint64

Headers

X-APTOS-CHAIN-ID

integer format: uint8

Chain ID of the current chain

X-APTOS-LEDGER-VERSION

integer format: uint64

Current ledger version of the chain

X-APTOS-LEDGER-OLDEST-VERSION

integer format: uint64

Oldest non-pruned ledger version of the chain

X-APTOS-LEDGER-TIMESTAMPUSEC

integer format: uint64

Current timestamp of the chain

X-APTOS-EPOCH

integer format: uint64

Current epoch of the chain

X-APTOS-BLOCK-HEIGHT

integer format: uint64

Current block height of the chain

X-APTOS-OLDEST-BLOCK-HEIGHT

integer format: uint64

Oldest non-pruned block height of the chain

X-APTOS-GAS-USED

integer format: uint64

The cost of the call in terms of gas

404

application/json

This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.

object

message

required

A message describing the error

string

error_code

required

These codes provide more granular error information beyond just the HTTP status code of the response.

string

Allowed values: account_not_found resource_not_found module_not_found struct_field_not_found version_not_found transaction_not_found table_item_not_found block_not_found state_value_not_found version_pruned block_pruned invalid_input invalid_transaction_update sequence_number_too_old vm_error rejected_by_filter health_check_failed mempool_is_full internal_error web_framework_error bcs_not_supported api_disabled

vm_error_code

A code providing VM error details when submitting transactions to the VM

integer format: uint64

Headers

X-APTOS-CHAIN-ID

integer format: uint8

Chain ID of the current chain

X-APTOS-LEDGER-VERSION

integer format: uint64

Current ledger version of the chain

X-APTOS-LEDGER-OLDEST-VERSION

integer format: uint64

Oldest non-pruned ledger version of the chain

X-APTOS-LEDGER-TIMESTAMPUSEC

integer format: uint64

Current timestamp of the chain

X-APTOS-EPOCH

integer format: uint64

Current epoch of the chain

X-APTOS-BLOCK-HEIGHT

integer format: uint64

Current block height of the chain

X-APTOS-OLDEST-BLOCK-HEIGHT

integer format: uint64

Oldest non-pruned block height of the chain

X-APTOS-GAS-USED

integer format: uint64

The cost of the call in terms of gas

413

application/json

This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.

object

message

required

A message describing the error

string

error_code

required

These codes provide more granular error information beyond just the HTTP status code of the response.

string

Allowed values: account_not_found resource_not_found module_not_found struct_field_not_found version_not_found transaction_not_found table_item_not_found block_not_found state_value_not_found version_pruned block_pruned invalid_input invalid_transaction_update sequence_number_too_old vm_error rejected_by_filter health_check_failed mempool_is_full internal_error web_framework_error bcs_not_supported api_disabled

vm_error_code

A code providing VM error details when submitting transactions to the VM

integer format: uint64

Headers

X-APTOS-CHAIN-ID

integer format: uint8

Chain ID of the current chain

X-APTOS-LEDGER-VERSION

integer format: uint64

Current ledger version of the chain

X-APTOS-LEDGER-OLDEST-VERSION

integer format: uint64

Oldest non-pruned ledger version of the chain

X-APTOS-LEDGER-TIMESTAMPUSEC

integer format: uint64

Current timestamp of the chain

X-APTOS-EPOCH

integer format: uint64

Current epoch of the chain

X-APTOS-BLOCK-HEIGHT

integer format: uint64

Current block height of the chain

X-APTOS-OLDEST-BLOCK-HEIGHT

integer format: uint64

Oldest non-pruned block height of the chain

X-APTOS-GAS-USED

integer format: uint64

The cost of the call in terms of gas

500

application/json

This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.

object

message

required

A message describing the error

string

error_code

required

These codes provide more granular error information beyond just the HTTP status code of the response.

string

Allowed values: account_not_found resource_not_found module_not_found struct_field_not_found version_not_found transaction_not_found table_item_not_found block_not_found state_value_not_found version_pruned block_pruned invalid_input invalid_transaction_update sequence_number_too_old vm_error rejected_by_filter health_check_failed mempool_is_full internal_error web_framework_error bcs_not_supported api_disabled

vm_error_code

A code providing VM error details when submitting transactions to the VM

integer format: uint64

Headers

X-APTOS-CHAIN-ID

integer format: uint8

Chain ID of the current chain

X-APTOS-LEDGER-VERSION

integer format: uint64

Current ledger version of the chain

X-APTOS-LEDGER-OLDEST-VERSION

integer format: uint64

Oldest non-pruned ledger version of the chain

X-APTOS-LEDGER-TIMESTAMPUSEC

integer format: uint64

Current timestamp of the chain

X-APTOS-EPOCH

integer format: uint64

Current epoch of the chain

X-APTOS-BLOCK-HEIGHT

integer format: uint64

Current block height of the chain

X-APTOS-OLDEST-BLOCK-HEIGHT

integer format: uint64

Oldest non-pruned block height of the chain

X-APTOS-GAS-USED

integer format: uint64

The cost of the call in terms of gas

503

application/json

This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.

object

message

required

A message describing the error

string

error_code

required

These codes provide more granular error information beyond just the HTTP status code of the response.

string

Allowed values: account_not_found resource_not_found module_not_found struct_field_not_found version_not_found transaction_not_found table_item_not_found block_not_found state_value_not_found version_pruned block_pruned invalid_input invalid_transaction_update sequence_number_too_old vm_error rejected_by_filter health_check_failed mempool_is_full internal_error web_framework_error bcs_not_supported api_disabled

vm_error_code

A code providing VM error details when submitting transactions to the VM

integer format: uint64

Headers

X-APTOS-CHAIN-ID

integer format: uint8

Chain ID of the current chain

X-APTOS-LEDGER-VERSION

integer format: uint64

Current ledger version of the chain

X-APTOS-LEDGER-OLDEST-VERSION

integer format: uint64

Oldest non-pruned ledger version of the chain

X-APTOS-LEDGER-TIMESTAMPUSEC

integer format: uint64

Current timestamp of the chain

X-APTOS-EPOCH

integer format: uint64

Current epoch of the chain

X-APTOS-BLOCK-HEIGHT

integer format: uint64

Current block height of the chain

X-APTOS-OLDEST-BLOCK-HEIGHT

integer format: uint64

Oldest non-pruned block height of the chain

X-APTOS-GAS-USED

integer format: uint64

The cost of the call in terms of gas

507

application/json

This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.

object

message

required

A message describing the error

string

error_code

required

These codes provide more granular error information beyond just the HTTP status code of the response.

string

Allowed values: account_not_found resource_not_found module_not_found struct_field_not_found version_not_found transaction_not_found table_item_not_found block_not_found state_value_not_found version_pruned block_pruned invalid_input invalid_transaction_update sequence_number_too_old vm_error rejected_by_filter health_check_failed mempool_is_full internal_error web_framework_error bcs_not_supported api_disabled

vm_error_code

A code providing VM error details when submitting transactions to the VM

integer format: uint64

Headers

X-APTOS-CHAIN-ID

integer format: uint8

Chain ID of the current chain

X-APTOS-LEDGER-VERSION

integer format: uint64

Current ledger version of the chain

X-APTOS-LEDGER-OLDEST-VERSION

integer format: uint64

Oldest non-pruned ledger version of the chain

X-APTOS-LEDGER-TIMESTAMPUSEC

integer format: uint64

Current timestamp of the chain

X-APTOS-EPOCH

integer format: uint64

Current epoch of the chain

X-APTOS-BLOCK-HEIGHT

integer format: uint64

Current block height of the chain

X-APTOS-OLDEST-BLOCK-HEIGHT

integer format: uint64

Oldest non-pruned block height of the chain

X-APTOS-GAS-USED

integer format: uint64

The cost of the call in terms of gas