Pins
Replace a pin request
Replaces the old request with a new queued request and returns its new requestid. If name is omitted or empty, the old name is retained. Filebase responds with HTTP 200, although retrieval remains asynchronous. The old pin record is removed during replacement; do not assume its content stays pinned until the new pin completes. If continuity is required, create a separately named pin, wait for pinned, update references, then delete the old request. Poll the new requestid, not the old one.
post/pins/{requestid}
Request
- Base URL: https://api.filebase.io/v1/ipfs
- URL: https://api.filebase.io/v1/ipfs/pins/{requestid}
- Auth: HTTP bearer
Request body
Example request
{
"cid": "bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi",
"name": "example.txt",
"origins": [],
"meta": {
"app": "example"
}
}Response
Replacement created; use its new requestid to poll completion.
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.