IPFS · Authentication Profile

Ipfs Authentication

Authentication

IPFS secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

IPFSDistributed StorageContent-AddressedDecentralizedPeer-to-PeerFile StorageDAGPinningGateway
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

accessToken http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/ipfs-pinning-service-api.yaml
summary:
  types:
  - http
schemes:
- name: accessToken
  type: http
  scheme: bearer
  description: |-
    An opaque token is required to be sent with each request in the HTTP header:
    - `Authorization: Bearer <access-token>`

    The `access-token` should be generated per device, and the user should have the ability to revoke each token separately.
  sources:
  - openapi/ipfs-pinning-service-api.yaml