ipfs/kubo

Expose /api/v0/id on the gateway

Open

#3759 opened on Mar 7, 2017

View on GitHub
 (3 comments) (1 reaction) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedneed/analysistopic/gateway

Description

It seems it is not exposed: https://gateway.ipfs.io/api/v0/id?arg=QmULgY72aAJ4W7Nxb2qpxAGQXsFCFfaQc9qgAsmkvx8YPS

Contributor guide

Tech stack
go
Domain
backendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GoIPFS architectureHTTP API design
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine how existing gateway endpoints like /api/v0/version are implemented in the kuborepo, likely in the gateway package. The /id endpoint should expose the node's identity by calling the appropriate IPFS API. Look at the command handler for 'ipfs id' and replicate its logic on the gateway side.