# Api Documentation self host

**URL:** <https://community.postman.com/t/api-documentation-self-host/3622>\
**Category:** Help Hub\
**Tags:** api-documentation\
**Created:** [December 17, 2018, 9:51pm UTC](https://community.postman.com/t/api-documentation-self-host/3622 "2018-12-17T21:51:50Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![development](https://avatars.discourse-cdn.com/v4/letter/d/7feea3/32.png) [@development](https://community.postman.com/u/development)\
**Post date:** [December 17, 2018, 9:51pm UTC](https://community.postman.com/t/api-documentation-self-host/3622/1 "2018-12-17T21:51:50Z")

</div>

I am using postman pro for api documentation. I would like to self host or locally spit out the documentation to put on my server. Is this possible? If so how is this done? Thank you.

---

<div class="post-metadata">

**Author:** ![jetison](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/jetison/32/12_2.png) [@jetison](https://community.postman.com/u/jetison)\
**Post date:** [December 18, 2018, 6:00pm UTC](https://community.postman.com/t/api-documentation-self-host/3622/2 "2018-12-18T18:00:02Z")

</div>

You can host the documentation on your custom domain, but there’s not currently a way to self host.

To spit it out locally, you can [export the underlying collection as JSON](https://learning.getpostman.com/docs/postman/collections/data_formats#exporting-and-importing-postman-data), but it would be a manual process to convert that to your documentation HTML. As an alternative, some folks will embed the collection as a [Run in Postman button](https://learning.getpostman.com/docs/postman_for_publishers/run_button/creating_run_button) on their internal developer portals or wikis, but it sounds like you’re looking for the fully rendered documentation.

---

<div class="post-metadata">

**Author:** ![development](https://avatars.discourse-cdn.com/v4/letter/d/7feea3/32.png) [@development](https://community.postman.com/u/development)\
**Post date:** [December 21, 2018, 5:08pm UTC](https://community.postman.com/t/api-documentation-self-host/3622/3 "2018-12-21T17:08:16Z")

</div>

Thank you for you response, unfortunately either of those solutions will not work for me. But, is there a plan to have postman spit out documentation as a fully rendered document in the works?

---

<div class="post-metadata">

**Author:** ![jetison](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/jetison/32/12_2.png) [@jetison](https://community.postman.com/u/jetison)\
**Post date:** [December 21, 2018, 6:32pm UTC](https://community.postman.com/t/api-documentation-self-host/3622/4 "2018-12-21T18:32:38Z")

</div>

I don’t believe so. But you’re welcome to [submit a feature request](https://github.com/postmanlabs/postman-app-support/issues?q=is%3Aopen+is%3Aissue+label%3AFeature) or upvote an existing one.

---

<div class="post-metadata">

**Author:** ![fabio.serra](https://avatars.discourse-cdn.com/v4/letter/f/ecccb3/32.png) [@fabio.serra](https://community.postman.com/u/fabio.serra)\
**Post date:** [July 4, 2019, 11:20am UTC](https://community.postman.com/t/api-documentation-self-host/3622/5 "2019-07-04T11:20:33Z")

</div>

I don’t understand why one of the most useful feature is still not implemented. There isn’t a way to publish the documentation for external developers in our own domain password protected.

---

<div class="post-metadata">

**Author:** ![antonakos](https://avatars.discourse-cdn.com/v4/letter/a/a88e57/32.png) [@antonakos](https://community.postman.com/u/antonakos)\
**Post date:** [July 5, 2019, 9:25am UTC](https://community.postman.com/t/api-documentation-self-host/3622/6 "2019-07-05T09:25:53Z")

</div>

Hello there,

I am trying to export the Postman collection using an API key:

```auto
curl https://api.getpostman.com/collections/<collection-uid> -H 'X-Api-Key: <api-key>'

```

Unfortunately the downloaded JSON file seems to be in the deprecated format of **v1** instead of the latest **v2.1** one. Is there a way to export the collection in the latest version?

---

<div class="post-metadata">

**Author:** ![antonakos](https://avatars.discourse-cdn.com/v4/letter/a/a88e57/32.png) [@antonakos](https://community.postman.com/u/antonakos)\
**Post date:** [July 5, 2019, 4:03pm UTC](https://community.postman.com/t/api-documentation-self-host/3622/7 "2019-07-05T16:03:55Z")

</div>

I just figured out the problem. **Postman API** exports the collection as follows:

> **{  
> “collection”:{**  
> “info”:{…

Whereas the **manual export** of the collection using Postman App does _NOT_ wrap it in a **collection** JSON object.

I would expect that Postman API’s response would be identical to the one triggered manually. Is there any way I receive the unwrapped payload using Postman API?

---

<div class="post-metadata">

**Author:** ![dmitri](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@dmitri](https://community.postman.com/u/dmitri)\
**Post date:** [December 2, 2020, 12:52pm UTC](https://community.postman.com/t/api-documentation-self-host/3622/8 "2020-12-02T12:52:03Z")

</div>

This should generate web friendly documentation out of postman collection

> **[GitHub - aubm/postmanerator: A HTTP API documentation generator that use...](https://github.com/aubm/postmanerator)**
>
> A HTTP API documentation generator that use Postman collections - GitHub - aubm/postmanerator: A HTTP API documentation generator that use Postman collections