Upload meta-address
POST /api/v1/ipfs/upload validates meta-address hex and uploads bytes through Pinata v3.Retrieve raw bytes
GET /api/v1/ipfs/:cid returns application/octet-stream from backend proxy.Endpoints
POST /api/v1/ipfs/uploadGET /api/v1/ipfs/:cid
Upload request schema
Hex-encoded SPECTER meta-address.
Optional display/pin name sent to Pinata upload API.
Upload response schema
Uploaded IPFS content identifier.
Formatted value for name service storage, e.g.
ipfs://<cid>.Retrieve request params
CID to retrieve through backend gateway client.
Typical flow
Example calls
- Upload (cURL)
- Retrieve (cURL)
- JavaScript
Required environment variables
Required environment variables
Upload requires
PINATA_JWT. Retrieval requires PINATA_GATEWAY_URL and PINATA_GATEWAY_TOKEN.Gateway and caching behavior
Gateway and caching behavior
Downloads use configured dedicated gateway and can be cached in-memory by CID when cache is enabled.
Response content type for GET
Response content type for GET
GET /api/v1/ipfs/:cid responds with raw bytes and Content-Type: application/octet-stream.