Currently, Document360 allows linking to headings across workspaces, including within API documentation; however, it is not possible to link directly to specific fields within an endpoint’s response schema (such as nested properties). The customer requires the ability to create direct links from documentation, to individual fields within the response schema.
At present, since schema fields are dynamically generated from the API specification, they cannot be individually referenced, which limits navigation. Enabling anchor links for response schema fields would significantly improve usability, allowing users to directly navigate to precise fields and making documentation more scalable for teams managing frequently updated APIs.