Wetez
  • Hello
  • Invite Wetez
  • User
    • Staking
      • Polygon
      • Cosmos
      • Oasis
      • Mina
      • Evmos
      • Tezos
      • Solana
      • Kava
      • Akash
      • Juno
      • IRISnet
      • Ethereum
      • IoTex
      • Wanchain
      • Gravity Bridge
      • Meter
      • ChainX
      • Edgeware
      • Debio Network
      • Myriad
      • IOST
      • Rebus
      • Teritori
      • Carbon
      • Canto
      • OmniFlix(Coming soon)
      • Projects inactive
        • Polkadot
        • Nym Mixnode
        • Polkadex
        • Findora
        • Sifchain
        • Alaya
        • NFTmart
        • Umee
    • Metamask RPCs
    • IPFS Pinning
  • Developer
    • Appchain
      • Cosmos SDK Chain
      • Substrate Independent Chain
      • Polkadot Parachain
      • Polygon Edge Chain
      • Ethereum Rollups
      • Avalanche Subnet
      • Oasis Paratime
      • BNB Sidechain
    • APIs
      • Ethereum Mainnet
      • Solana Mainnet
      • Polygon Mainnet
      • Arbitrum Mainnet
      • Tendermint Mainnet
      • Error
    • Storage
      • IPFS
      • HTTP API methods
      • add
      • block_get
      • block_put
      • block_stat
      • cat
      • dag_get
      • dag_put
      • dag_resolve
      • get
      • pin_add
      • pin_ls
      • pin_rm
      • pin_update
      • version
Powered by GitBook
On this page
  • Arguments
  • NDJSON responses
  1. Developer
  2. Storage

HTTP API methods

The IPFS documentation lists the IPFS HTTP API methods.

Wetez supports a subset of these which are detailed in this section.

All Wetez IPFS methods require including the Admin Key or use Dedicated Gateway

Arguments

Arguments are added through the special query string key arg:

curl -X POST "https://mainnet-rpc.wetez.io/ipfs/$AdminKey/api/v0/add?recursive=false&quiet=<value>&quieter=<value>&silent=<value>&progress=<value>&trickle=<value>&only-hash=<value>&wrap-with-directory=<value>&hidden=<value>&chunker=<value>&pin=true&raw-leaves=<value>&nocopy=<value>&fscache=<value>&cid-version=0&hash=sha2-256"

Note that arg can be used multiple times to signify multiple arguments.

NDJSON responses

When a bunch of objects are requested, IPFS returns them in the Newline Delimited JSON, NDJSON, format.

This is because the calls are asynchronous and the responses are processed one object at a time.

Response JSON includes \n separators that must be dealt with.

PreviousIPFSNextadd

Last updated 2 years ago