POST
/
v1
/
ipfs
/
pins
/
pinfiles
curl --request POST \
  --url https://api.chainstack.com/v1/ipfs/pins/pinfiles \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: multipart/form-data' \
  --form 'bucket_id=<string>' \
  --form 'folder_id=<string>'
[
  {
    "id": "<string>",
    "cid": "<string>",
    "type": "<string>",
    "title": "<string>",
    "status": "<string>",
    "size": 123,
    "item_count": 123,
    "created_at": "2023-11-07T05:31:56Z",
    "updated_at": "2023-11-07T05:31:56Z",
    "bucket_id": "<string>",
    "folder_id": "<string>",
    "public_link": "<string>",
    "owner": {
      "id": "<string>",
      "name": "<string>"
    },
    "creator": {
      "id": "<string>",
      "name": "<string>"
    }
  }
]

Authorizations

Authorization
string
header
required

Chainstack API uses API keys to authenticate requests. You can view and manage your API keys in the platform UI. Your API keys carry many privileges, so be sure to keep them secure! Provide your API key as the Authorization header. The value of the header consists of Bearer prefix and secret key generated through the platform UI.

curl -X GET 'https://api.chainstack.com/v1/organization/' \
--header 'Authorization: Bearer FX7CWlLg.FMpAO8cgCX2N7s41EncRru2nb5CmTZUt'

All API requests must be made over HTTPS.

Body

multipart/form-data
bucket_id
string
required
file
file
required
folder_id
string

optional, if not set, files uploaded to root of bucket

Response

200
application/json
success
id
string
cid
string
type
string
title
string
status
string
size
integer
item_count
integer
created_at
string
updated_at
string
bucket_id
string
folder_id
string
owner
object
creator
object