OpenAPI v3 "Links" - Stoplight | Product Roadmap

Stoplight

API Specifications

Protocol Buffers

Governance

Quality dashboard

Lifecycle Stages

Spectral: AutoFix Style Issues (CLI/Studio)

API Design Reviews

Show Spectral results in Form view

Create new file from a template

Collaboration

Create a pull request from Studio

Notifications - Activity Summary, Breaking Changes, etc

Integrate with team chat apps (Slack, Microsoft Teams, Discord, etc)

User Management / Audit

Do you want SCIM supported to simplify user (de)provisioning process? How would you use SCIM?

Personal Access Tokens

Design

Persisted Mock Data

Rewrite references and links

Keyboard Shortcuts

Referencing paths and operations

Learning & Recording

Autocomplete ref in code editor

Studio Plugin System

Abstract Object to Model

Reporting, Analytics, and Metrics

Move Shared to Standalone Models

OAS Dictionary Support

OpenAPI v3 "Links"

Support nested/inner schema definitions

Support for polymorphism using OpenAPI v3 discriminators

Visual Diagram Editing

Docs

Elements for Internal Projects

Table of Contents Editor

Custom templating for code samples

Custom Variables

Was this page helpful?

Custom Link Preview Title & Description

Dark Theme for Docs

Automatic Changelogs

Try It Auth: OpenID Connect

Integrated Vale Support

Integrate with Google Analytics Site Search

Docs: Try It CORS Proxy

Today try it requests fail if the API doesn't allow cross origin requests. This feature would pipe requests through a proxy allowing requests to successfully go through to APIs that don't allow CORS requests.

Embed Custom JS Snippet

Improve Discoverability / Search

Try It Auth: Generate OAuth 2.0 Tokens

Try It: Cookie Support

Support Tag Descriptions

Product Management Software by Productboard

OpenAPI v3 "Links"

35

CL

Chris Lott

Posted on March 2020

Render links in Docs to let folks know that an API response can be used in a workflow of multiple requests. One response contains information that can be used to make the next request, which could be HATEOAS (turning your API into a state machine) or just making pagination options a bit more clear.