Catalog endpoints with a JSON list pin
List APIs, webhooks, or feature flags as a JSON list pin—scannable rows for ops and engineering without another spreadsheet tab.
When integrations multiply, endpoint lists rot in wikis. A JSON list pin displays an array of objects—method, path, owner, status—in a table-like view purpose-built for structured lists on the canvas.
Example: endpoint catalog pin
Loading JSON list viewer...
Why JSON list pins?
Uniform rows
Each object is one integration line item.
Easy to generate
Export from OpenAPI or ask AI to draft rows, then pin.
Complements JSON viewer
List = inventory; viewer = sample payload depth.
Getting started
Define fields your team cares about (name, path, owner). Build the array, create a JSON list pin, paste JSON. Refresh when services change.
Frequently Asked Questions (FAQ)
List vs table pin?
Table for human editing; JSON list when data is already JSON or agent-generated.
How many rows?
Keep under ~20 on shared canvases for scanability.
Version control?
Note API version in a column or caption.