dbc-pool-submit
curl --request POST \
--url https://api.jup.ag/studio/v1/dbc-pool/submit \
--header 'Content-Type: multipart/form-data' \
--header 'x-api-key: <api-key>' \
--form 'transaction=<string>' \
--form 'owner=<string>' \
--form 'content=<string>' \
--form headerImage='@example-file'{
"success": true,
"data": {
"mint": "TokenMintAddressExample111111111111111111111",
"configKey": "ConfigKeyAddressExample11111111111111111111"
}
}Studio
DBC Pool Submit
Execute the signed transaction, and optionally upload content and header image
POST
/
dbc-pool
/
submit
dbc-pool-submit
curl --request POST \
--url https://api.jup.ag/studio/v1/dbc-pool/submit \
--header 'Content-Type: multipart/form-data' \
--header 'x-api-key: <api-key>' \
--form 'transaction=<string>' \
--form 'owner=<string>' \
--form 'content=<string>' \
--form headerImage='@example-file'{
"success": true,
"data": {
"mint": "TokenMintAddressExample111111111111111111111",
"configKey": "ConfigKeyAddressExample11111111111111111111"
}
}Authorizations
Get API key via https://developers.jup.ag/portal
Body
multipart/form-data
- Base64-encoded signed transaction
- Owner wallet public key
- Optional content description displayed on Studio dedicated token page
- This is stored off-chain for our frontend to display
- This is NOT the on-chain token metadata
- The on-chain token metadata is done by making a PUT request to the presigned URL
- Optional header image file displayed on Studio token page
- This is stored off-chain for our frontend to display
- This is NOT the on-chain token metadata
- The on-chain token metadata is done by making a PUT request to the presigned URL
Was this page helpful?
⌘I
