IPFS RPC API

Legacy: This page documents Filebase's IPFS tier. For new deployments, use the S3-compatible object storage tier with the s3.filebase.io endpoint.

Filebase exposes a subset of the Kubo IPFS HTTP RPC API, letting tools that target the Kubo daemon talk to Filebase directly.

Base URL

https://rpc.filebase.io

Authentication

Generate an API key in the Access Keys console — keys are bucket-specific. Pass it as a Bearer token:

Authorization: Bearer <api-key>

IPFS CLI integration

Use the IPFS CLI directly with Filebase by passing the --api flag:

ipfs --api="/dns4/rpc.filebase.io/tcp/443/https" \
  --api-auth="<api-key>" \
  add ./file.txt

Endpoints

Path	Method	Description
/api/v0/add	POST	Add (and pin) a file.
/api/v0/pin/add	POST	Pin a CID.
/api/v0/pin/rm	POST	Unpin a CID.
/api/v0/pin/ls	POST	List pinned CIDs.
/api/v0/version	POST	Daemon version info.
/api/v0/dag/get	POST	Fetch a DAG node.
/api/v0/object/get	POST	Fetch an object.
/api/v0/cat	POST	Stream a file's bytes by CID.

Example: list pins

curl -X POST \
  -H "Authorization: Bearer <api-key>" \
  https://rpc.filebase.io/api/v0/pin/ls

What's next

• Pinning Service API
• Pinning files