Pins
Pin an existing CID
Queues retrieval and recursive pinning of an existing CID. An omitted or empty name defaults to the CID. Submitting the same name and CID again returns the existing pin and requestid with HTTP 202; it does not create a second request. Reusing a name with a different CID returns HTTP 409. Use a distinct name or explicitly replace the existing pin. HTTP 202 does not guarantee completion; poll the returned requestid. A retry returning an existing failed pin does not restart it.
post/pins
Request
- Base URL: https://api.filebase.io/v1/ipfs
- URL: https://api.filebase.io/v1/ipfs/pins
- Auth: HTTP bearer
Request body
Example request
{
"cid": "bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi",
"name": "example.txt",
"origins": [],
"meta": {
"app": "example"
}
}Response
New request accepted, or the existing pin with the same name and CID returned.
Example response
{
"requestid": "opaque-pin-request-id",
"status": "queued",
"created": "2026-09-30T12:00:00Z",
"pin": {
"cid": "bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi",
"name": "example.txt",
"origins": [],
"meta": {
"app": "example"
}
},
"delegates": [],
"info": {
"size": "0"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.