How do I set anchors for the postman documentation?












1















I make the documentation for api, how to make a cross reference (named anchor) with markdown in postman?



Is there such a similar option?



Take me to <a href="#api"> rest api </a> ... <a name="api"> this is rest api </a>









share|improve this question





























    1















    I make the documentation for api, how to make a cross reference (named anchor) with markdown in postman?



    Is there such a similar option?



    Take me to <a href="#api"> rest api </a> ... <a name="api"> this is rest api </a>









    share|improve this question



























      1












      1








      1








      I make the documentation for api, how to make a cross reference (named anchor) with markdown in postman?



      Is there such a similar option?



      Take me to <a href="#api"> rest api </a> ... <a name="api"> this is rest api </a>









      share|improve this question
















      I make the documentation for api, how to make a cross reference (named anchor) with markdown in postman?



      Is there such a similar option?



      Take me to <a href="#api"> rest api </a> ... <a name="api"> this is rest api </a>






      postman






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jul 15 '18 at 9:49









      Pearly Spencer

      12.1k173968




      12.1k173968










      asked Jul 13 '18 at 9:18









      NiraxNirax

      64




      64
























          1 Answer
          1






          active

          oldest

          votes


















          0














          You could create an element with an id "api" in a collection/folder/request description, and then link it in another place like [rest api](#api)



          If you want to link a folder or request, you should get the ID (from the documentation itself) and then using the same Markdown as before with the respective ID.



          Note: Take into account that Postman Documentation doesn't provide (at this moment) a way to specify a custom ID for a folder or request, so in case you're trying to do that, the best you can do is create an element with an id at the top of the description and then linking to that new element. It will scroll to a point under the title, which may result in a poorer user experience.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f51321753%2fhow-do-i-set-anchors-for-the-postman-documentation%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            You could create an element with an id "api" in a collection/folder/request description, and then link it in another place like [rest api](#api)



            If you want to link a folder or request, you should get the ID (from the documentation itself) and then using the same Markdown as before with the respective ID.



            Note: Take into account that Postman Documentation doesn't provide (at this moment) a way to specify a custom ID for a folder or request, so in case you're trying to do that, the best you can do is create an element with an id at the top of the description and then linking to that new element. It will scroll to a point under the title, which may result in a poorer user experience.






            share|improve this answer




























              0














              You could create an element with an id "api" in a collection/folder/request description, and then link it in another place like [rest api](#api)



              If you want to link a folder or request, you should get the ID (from the documentation itself) and then using the same Markdown as before with the respective ID.



              Note: Take into account that Postman Documentation doesn't provide (at this moment) a way to specify a custom ID for a folder or request, so in case you're trying to do that, the best you can do is create an element with an id at the top of the description and then linking to that new element. It will scroll to a point under the title, which may result in a poorer user experience.






              share|improve this answer


























                0












                0








                0







                You could create an element with an id "api" in a collection/folder/request description, and then link it in another place like [rest api](#api)



                If you want to link a folder or request, you should get the ID (from the documentation itself) and then using the same Markdown as before with the respective ID.



                Note: Take into account that Postman Documentation doesn't provide (at this moment) a way to specify a custom ID for a folder or request, so in case you're trying to do that, the best you can do is create an element with an id at the top of the description and then linking to that new element. It will scroll to a point under the title, which may result in a poorer user experience.






                share|improve this answer













                You could create an element with an id "api" in a collection/folder/request description, and then link it in another place like [rest api](#api)



                If you want to link a folder or request, you should get the ID (from the documentation itself) and then using the same Markdown as before with the respective ID.



                Note: Take into account that Postman Documentation doesn't provide (at this moment) a way to specify a custom ID for a folder or request, so in case you're trying to do that, the best you can do is create an element with an id at the top of the description and then linking to that new element. It will scroll to a point under the title, which may result in a poorer user experience.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 2 at 15:06









                Nicolas OrchowNicolas Orchow

                12




                12
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f51321753%2fhow-do-i-set-anchors-for-the-postman-documentation%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    MongoDB - Not Authorized To Execute Command

                    How to fix TextFormField cause rebuild widget in Flutter

                    in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith