Public developer hub and catalog sharing
Matar Peles
Like in Notion or Google Docs, Port’s dashboards and pages can contain unique data to share between people.
This feature will allow creating a separate public Port page or an external-facing developer hub to share API catalogs, documentation, and insights with external developers or partners using a link.
Aidan O'Connor
Port is great for serving as an internal API marketplace for internal developers to discover and collaborate on existing APIs instead of duplicating business logic.
However, many ecommerce companies expose their APIs to external developers as well, and the existing solutions can be lacking.
To best serve companies that desire to effectively expose their APIs to external developers, Port should consider extending this feature idea to include a few things:
- The ability to log into an API marketplace as a trusted external developer seeking to work with the APIs exposed by another company
- The ability to view the different versions of different APIs that are available to me as an external developer
- The ability to review documentation for all APIs that are available to me as an external developer
- The ability to easily expose a new version of an API to external developers, as an internal developer that works on such APIs
- The ability to easily request access to APIs to which I do not currently have access, as an external developer
- The ability to easily grant access to certain APIs to external developers, as an internal developer
C
Christopher Newsome
Example use case:
API Catalog / Management - share catalog list of APIs with visibility into health checks of those APIs to both internal and external developers consuming those APIs