Skip to main content
POST
Save (and optionally relay) the signed launch transactions

Body

application/json
deploymentId
string
required
owner
string
required

Base58 Solana address.

Pattern: ^[1-9A-HJ-NP-Za-km-z]{32,44}$
Example:

"So11111111111111111111111111111111111111112"

baseMint
string
required

Base58 Solana address.

Pattern: ^[1-9A-HJ-NP-Za-km-z]{32,44}$
Example:

"So11111111111111111111111111111111111111112"

pool
string
required

Base58 Solana address.

Pattern: ^[1-9A-HJ-NP-Za-km-z]{32,44}$
Example:

"So11111111111111111111111111111111111111112"

config
string
required

Base58 Solana address.

Pattern: ^[1-9A-HJ-NP-Za-km-z]{32,44}$
Example:

"So11111111111111111111111111111111111111112"

configTransaction
object | null
required

Required exactly when configSource is "creator".

poolTransaction
object
required
relay
boolean

Let the server broadcast the verified wires (config first, then the pool once the config is confirmed).

Response

Saved.

saved
any
required
state
enum<string>
required
Available options:
signed,
unknown,
config_landed,
confirmed,
failed,
expired
relayed
object | null
required