Is there a 'copy path' like feature to get the full path to a request from the root folder?

I have a big shared collection with folders and subfolders with subfolders… etc. How do I get the full path of a request so a coworker can easily find it? I have many requests with same names so teh search feature is not going to be very helpful.

Similar to copy path in Windows file explorer.

Hello @thenrich2009, Welcome to the Postman community :smiley:

To get the path of your request, you can use the small link icon on the Postman request builder page [as shown in the fig].


1 Like

How do I go to the request once I have a url? There’s nothing that looks like an address bar. Nothing in the menus. I searched the docs for ’ go to url’. ‘Go to bookmark’. ‘Go to link’. Nothing!

If the Collection is shared, you could use the Comments feature on the Collection/Folder/Request and tag your team mates.

This will send a notification (email and in-app) to your team mates, containing a button that will lead to that element.

That might work for some people but not for me. I want to put the link in some documentation or put it in a DevOps story to be used later.

Also, I would rather see a feature with a breadcrumbs type of links like:
My collections1/folder1/subfolder2/subfolder3/request1.

So that if the request gets recreated, and original url gets broken, the user can still get to the request by looking at the breadcrumbs path. It’s not tied to a hardcoded link.

The issue with this is that it isn’t unique, as there is nothing stopping you from giving multiple collections/folders/requests the same name. I could have the same breadcrumb in the workspace for a different collection or a fork of the original, they would look the same. You can also have these Collections in different Workspace with the same name.

The entity link also includes the ids for those specific elements (Workspace, Collection, Folders, Request), to give them that uniqueness. The link attached to a doc would open Postman on the Web and show the same UI as it would in the app.

The thing that’s missing here is deep linking in the app itself, as you mentioned there currently isn’t a way to take that link and open the same place in the app, unless you’re making a comment on a specific element.