How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Filebase Pins API

IPFS pin management operations

Filebase Pins API is one of 15 APIs that Filebase publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Pins. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against a single base URL, https://api.filebase.io/v1/ipfs.

5 operations 2 paths 5 schemas 1 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://s3.filebase.io
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Filebase Pins API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Per-bucket Bearer token for authentication

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Pins 5

IPFS pin management operations

GET
/pins
List pin objects
listPins 8 params → 200400401429500
POST
/pins
Add pin object
addPin body → 202400401409429500
GET
/pins/{requestId}
Get pin object
getPin 1 param → 200401404429500
POST
/pins/{requestId}
Replace pin object
replacePin 1 param body → 202400401404409429500
DELETE
/pins/{requestId}
Remove pin object
deletePin 1 param → 202401404429500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are PinStatus (6 properties), Pin (4 properties), PinResults (2 properties), Failure (1 property). Each schema is shown below with its type and property counts.

Failure
object
1 property 1 required
PinStatus
object
6 properties 5 required
Status
string
Status of a pin object
Pin
object
4 properties 1 required
PinResults
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

filebase-pins-api-openapi.yml Raw ↑

Other APIs Filebase publishes across the network.

Filebase S3-Compatible API
Filebase Platform API
Filebase IPFS Pinning Service API
Filebase IPFS RPC API
Filebase Buckets API
Filebase Data Management API
Filebase IPNS API
Filebase Keypairs API
Filebase MFS API
Filebase Multipart Upload API
Filebase Node API
Filebase Objects API
Where this information came from

This is an independent, third-party profile of Filebase Pins API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.