API
This API will allow you to create 1SatOrdinals Single and Collection Tokens.
Common
An Api Key must be passed in the header of all requests see Authentication
Create a Token Studio Project for your Standalone - Collection
POST https://platform.taal.com/token-studio/api/v1/project/createcurl --location 'https://platform.taal.com/token-studio/api/v1/project/create' \
--header 'Apikey: ## VALID_API_KEY ##' \
--header 'Content-Type: application/json' \
--data '{
"name": "1satcol project 1718100516565",
"isFungible": false,
"type": "single", //"collection"
"tokenProtocol": "OneSatOrdinal"
}'
{
"success": boolean,
"data": {
"projectUid": <uid>
}
}Get a list of your Token Studio projects
It will return all projects associated with your API Key.
Get details for a specific project id
Returns a project for a valid project id.
URL Parameters
projectId
A valid project Id
Output creation
Creates an output (single, collection, collectinItem) in the project.
Single projects can only contain single/standalone outputs
Collection projects need first a collection output created and then one or several collectionItems linked to the initial collection output
Body Parameters
subType
'single' for standalone tokens in single projects
'collection' for the seed token in collection projects
'collectionItem' for each element linked to the collection
projectUid
projectUid
contentType
contentType depending on the desired output type (text, html or image)
b64File
Raw content formatted in b64
metadata
Output deletion
Deletes an output (single, collection, collectinItem) in the project.
Query Parameters
outputUid
A valid output Id
Output List
Returns all outputs for a valid project id.
Query Parameters
projectUid
A valid project Id
on-chain
Optional. If provided, the accepted values are 0/1 (false / true) to filter by outputs already broadcast
type
Optional. If provided, the accepted values are collection / collectionItem, to filter by a specific type of output
Unsigned Transaction creation
Creates an unsigned transaction ready to sign and then be broadcast.
Unsigned transactions can refer to different outputs as well as different UTXO to be used for funding it
Response JSON structure
Body Parameters
project Id
publicKey
List of output Ids
Funding txId
Output Index of the tx e.g. 1
Broadcast Transaction
Broadcast a signed transaction and returns its transaction Id
Response JSON structure
Body Parameters
Transaction Uid returned by the create transaction endpoint
Signed transaction ready to be broadcast
Last updated
Was this helpful?