POST
/
v1
/
collections
curl --request POST \
  --url https://dev.api.mufi.app/v1/collections \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '{
  "name": "<string>",
  "metadata": "<string>",
  "chain": "WestendAssetHub"
}'
{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "created_at": "2023-11-07T05:31:56Z",
  "updated_at": "2023-11-07T05:31:56Z",
  "collection_id": 123,
  "last_minted_item_id": 123,
  "is_soulbound": true,
  "chain": "WestendAssetHub",
  "error": "<string>",
  "project_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "name": "<string>",
  "status": "Pending",
  "owner": "<string>",
  "creator": "<string>"
}

Authorizations

​
x-api-key
string
header
required

The API Key you were given in the developer portal. API keys are associated with your organization's project application and can have read or write permissions and an optional expiration date.

Body

application/json
Detailed metadata and configuration settings for creating an NFT Collection. This includes essential information such as the collection name, chain type, and additional metadata required for blockchain processing. You are responsible for hosting the metadata and any assets associated with the collection in a publicly accessible location.
​
name
string
required
​
metadata
string
required
​
chain
enum<string>
required
Available options:
WestendAssetHub,
AssetHub

Response

201
application/json
A collection request was successfully created and will be created asynchronously (usually less than a minute).
​
id
string
required
​
created_at
string
required
​
updated_at
string
required
​
last_minted_item_id
number
required
​
is_soulbound
boolean
required
​
chain
enum<string>
required
Available options:
WestendAssetHub,
AssetHub
​
project_id
string
required
​
name
string
required
​
status
enum<string>
required
Available options:
Pending,
Processing,
Created,
CreatedWithMetadata,
Failed
​
collection_id
number | null
​
error
string | null
​
owner
string | null
​
creator
string | null