Initializes an instance of the Aptos client with the specified settings. This allows users to configure various aspects of the client, such as network and endpoints.
Optionalsettings: AptosSettingsOptional configuration settings for the Aptos client.
import { Aptos, AptosConfig, Network } from "@aptos-labs/ts-sdk";
async function runExample() {
// Create a new Aptos client with default settings
const config = new AptosConfig({ network: Network.TESTNET }); // Specify the network
const aptos = new Aptos(config);
console.log("Aptos client initialized:", aptos);
}
runExample().catch(console.error);
ReadonlyclientThe client instance the SDK uses. Defaults to `@aptos-labs/aptos-client
Optional ReadonlyclientOptional client configurations
Optional ReadonlyfaucetThe optional hardcoded faucet URL to send requests to instead of using the network
Optional ReadonlyfaucetOptional specific Faucet configurations
Optional ReadonlyfullnodeThe optional hardcoded fullnode URL to send requests to instead of using the network
Optional ReadonlyfullnodeOptional specific Fullnode configurations
Optional ReadonlyindexerThe optional hardcoded indexer URL to send requests to instead of using the network
Optional ReadonlyindexerOptional specific Indexer configurations
ReadonlynetworkThe Network that this SDK is associated with. Defaults to DEVNET
Optional ReadonlypepperThe optional hardcoded pepper service URL to send requests to instead of using the network
Optional ReadonlyproverThe optional hardcoded prover service URL to send requests to instead of using the network
Optional ReadonlytransactionOptional specific Transaction Generation configurations
Returns the URL endpoint to send the request to based on the specified API type. If a custom URL was provided in the configuration, that URL is returned. Otherwise, the URL endpoint is derived from the network.
The type of Aptos API to get the URL for. This can be one of the following: FULLNODE, FAUCET, INDEXER, PEPPER, PROVER.
import { Aptos, AptosConfig, Network, AptosApiType } from "@aptos-labs/ts-sdk";
const config = new AptosConfig({ network: Network.TESTNET });
const aptos = new Aptos(config);
async function runExample() {
// Getting the request URL for the FULLNODE API
const url = config.getRequestUrl(AptosApiType.FULLNODE);
console.log("Request URL for FULLNODE:", url);
}
runExample().catch(console.error);
Checks if the provided URL is a known pepper service endpoint.
The URL to check against the known pepper service endpoints.
import { Aptos, AptosConfig, Network } from "@aptos-labs/ts-sdk";
const config = new AptosConfig({ network: Network.TESTNET });
const aptos = new Aptos(config);
async function runExample() {
const url = "https://example.pepper.service"; // replace with a real pepper service URL
// Check if the URL is a known pepper service endpoint
const isPepperService = config.isPepperServiceRequest(url);
console.log(`Is the URL a known pepper service? ${isPepperService}`);
}
runExample().catch(console.error);
Checks if the provided URL is a known prover service endpoint.
The URL to check against known prover service endpoints.
A boolean indicating whether the URL is a known prover service endpoint.
import { Aptos, AptosConfig, Network } from "@aptos-labs/ts-sdk";
const config = new AptosConfig({ network: Network.TESTNET });
const aptos = new Aptos(config);
// Check if the URL is a known prover service endpoint
const url = "https://prover.testnet.aptos.dev"; // replace with a real URL if needed
const isProver = config.isProverServiceRequest(url);
console.log(`Is the URL a known prover service? ${isProver}`);
If a custom transaction submitter has been specified in the PluginConfig and IGNORE_TRANSACTION_SUBMITTER is false, this will return a transaction submitter that should be used instead of the default transaction submission behavior.
Represents the configuration settings for an Aptos SDK client instance. This class allows customization of various endpoints and client settings.
Example