Publish Multiple Collections to a custom url

[science695]

We have documentation for multiple different types of API calls for our clients, and we would like to publish more than 1 collection to a custom url.

It seems like it would be very useful to not be limited to only 1 collection shared per custom url / subdomain.

[postmanpp]

We are also looking for publishing multiple collections per custom url

[sankalp0o]

@science695 @postmanpp So if I understand you correctly, you want to publish your collections on www.your-domain.com/collection1 & www.your-domain.com/collection2?

[postmanpp]

My requirement is I want to publish collection1 and collection 2 on www.your-domain.com

[sankalp0o]

@postmanpp So you expect that the same page to contain documentation for both of the collections one after the other?

[postmanpp]

yes. that is correct

[sankalp0o]

Understood. Any reason for having two collections instead of a single one? You can group them in different folders if organisation was your only concern.

[postmanpp]

We have different teams working on different modules like Finance, Marketing, HR, Integrations etc. Each team will build their own collections. So we want to document all these collections on single page

[sankalp0o]

Ah, makes sense. We don't have any immediate plans for this but there have been a couple of requests around multiple collections and environments for published documentations. I'll keep you posted if and when we take this up.

[sankalp0o]

@godfrzero

[godfrzero]

@postmanpp This is already possible using the Postman API (just that it's not a feature available straight out of the box). Each of your teams can work on separate collections, and the "master" collection which is a collated version of the individual collections, can be updated via the Postman API. You can carry out the collation on a daily basis or something using Postman Monitors, or you can use one of our integrations to update the master collection when any of the child collections are updated.

[science695]

@sankalp0o My use case would appear to split from postmanapp.

I am interested in what you referenced with:

www.your-domain.com/collection1 & www.your-domain.com/collection2?

We have multiple clients, and often build custom apis for them. We would find it very useful to be able to publish multiple collections with different uris on the same domain: www.your-domain.com/special-client-a-import www.your-domain.com/special-client-b-import www.your-domain.com/normal-client-import ....

And if these 3 different api definitions were on the same page it could be very confusing.

[pdsorensen]

This is also relevant for use cases where you have different products with seperate API documentation right? Not just for clients.

So it could potentially allow something like:

• www.docs.robot-company.com/api/fluffy-robot
• www.docs.robot-company.com/api/old-robot
• www.docs.robot-company.com/api/new-robot

[a85]

@sankalp0o We'll need to build some sort of mapping configuration between APIs + Domains + Collections.

[gtnardy]

up

[badikumar]

This feature would be very useful at least to specify a specify path to a documentation. In our case:

docs.company.com/api/v1 docs.company.com/api/v2

etc...

[prvinuch]

Hi Guys, I just found a way to categorise the APIs using same collection. we do have an option to create folders under same collection, which can be used to categorise the APIs.

[deepaks-idnow]

This feature would be really helpful for the companies who have multiple products and would like to show the documentation of these products in one custom URL. Folders is not the right solution as it is a single page and if users want to search specific text in one product's documentation then they end up going to the next product's documentation because of the same collection.

[deepaks-idnow]

A good example is Postman documentation itself - https://learning.getpostman.com/docs/postman-pro/what-is-pro/ Postman, Postman-Pro, Postman-Enterprise and Postman for Publishers are 4 different products but all of them can be seen in the same tree in the left panel but all of them are different pages. I would like to do the same for our products

[rohanaceres]

Any news on this?

[frcake]

This would be a great addition! we have the same needs as well as a single large documentation clutters the environmental variables by a lot ending up in a very difficult to use API...

[maqsimum]

An API could have multiple requests with different methods. An API in Postman world gets converted to collection and multiple requests. A collection upon publishing becomes a unique URL.

One product could have multiple APIs i.e. login, profile, products, transactions etc. Any product which is meant for the developers would always be intending to publish its APIs to its consumers and thats where the companies need ability to publish all of its APIs with/without nesting in one single page under a single URL as an entry point, e.g. https://docs.github.com/en/rest/reference

[edu791]

3 years have passed since this issue and still it's not possible to publish multiple collections in one URL

[natekwilson]

This would make publishing public documentation so much easier. I'd be very excited if we could nest all the collection-docs we want under one domain. Especially since our pay-tier prohibits us from having more than one custom domain. Ease of documentation/share-ability is one of Postman's weaknesses compared to SwaggerHub/openAPI

[pyashish]

Need this feature too. Upvoting this.

[chandrashekar-cohesity]

Upvoting this.

[bitsofsteve]

This is a much-needed feature. Upvoting

[jagan123]

Upvoted. We have soap APIs and REST APIs. These are two different collections. Similarly, got different product with their own teams and API collections. It'd be great to have those in their own paths under same subdomain.

[SimoneDesantisAltravia]

One year later, we need this too. We have 30 different APIs and even the pro plan can't cover our need.

[adamtal3]

Upvoting - it's surprising there's no option to use a single custom domain with different paths for different collections. I now need to create multiple subdomains

[nbren007]

Strong Upvote - Implementing the feature for publishing multiple collections to custom URLs is a game-changer for us. It directly impacts our decision-making process for choosing a platform to host our APIs. Currently, the lack of this feature positions Postman as a non-starter for our company. Its availability would streamline our API management, enhance collaboration across teams, and significantly improve our workflow efficiency. This feature is the key deciding factor for our subscription commitment.