Skip to main content
POST
Upload a File
The V3 Upload endpoint currently does not support folder uploads. Please use the legacy pinFileToIPFS endpoint

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

multipart/form-data
network
enum<string>
default:private
required

Determine if the file should be uploaded to either the public or private IPFS network. If not designated it will default to private.

Available options:
public,
private
file
file
required

File object you want to upload

name
string

Add a custom name for the file

group_id
string

ID of the group you would like to upload

keyvalues
object

Add additional key value metadata to files upon upload

car
boolean

Upload a file as a raw CAR file (only supported for public network)

cid_version
enum<string>
default:v1

UnixFS import profile used to hash the upload. v1 (default) produces a CIDv1 (bafy…) with raw leaves, 256 KiB chunks and up to 174 links per node, matching ipfs add --cid-version=1. v0 produces a legacy CIDv0 (Qm…) with dag-pb leaves, matching ipfs add --cid-version=0. unixfs-v1-2025 produces a CIDv1 using the IPIP-499 profile — 1 MiB chunks and up to 1024 links per node — matching kubo's test-cid-v1-wide config profile. The profile is fixed when the upload is created and cannot be changed while resuming it.

Available options:
v0,
v1,
unixfs-v1-2025

Response

200 - application/json

Successful response

data
object