# 3.6.3.API Developer Portal

* Developer Portal ![](https://163116165-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4M0G7tIs4o9F9vSrao%2F-M4M0IVB0ax0vs2ocz_r%2F-M4M0YZrrdHKLbfng36n%2F%E6%9C%AA%E5%91%BD%E5%90%8D212.jpg?generation=1586302969816009\&alt=media)
* API documentation
  * Mange in Swagger/ OAI
    * Use externalDocs URL to connect with external documentation
    * Try it feature
      * Allow the developer to try over API on the developer portal without needing to write code
      * 幫助開始者了解API是如何運作的
    * Provide code sample, provide sample data
    * Provide SDK
    * [Walmart](https://developer.walmartlabs.com/io-docs)
* Manual provisioning
  * May work for internal teams
  * It's not suggested that you use this kind of a process for public or partner APIs in self provisioning

    ![](https://163116165-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4M0G7tIs4o9F9vSrao%2F-M4M0IVB0ax0vs2ocz_r%2F-M4M0YZtlqadw4GJQ5sM%2F%E6%9C%AA%E5%91%BD%E5%90%8D2123.jpg?generation=1586302969734475\&alt=media)
* Self provisioning
  * Self service + Auto approved suggested (if possible)

    ![](https://163116165-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4M0G7tIs4o9F9vSrao%2F-M4M0IVB0ax0vs2ocz_r%2F-M4M0YZvjQORpWutFNWo%2F%E6%9C%AA%E5%91%BD%E5%90%8D2124.jpg?generation=1586302969662661\&alt=media)
* Provisioning practices
  * Clearly define the role, responsible for authorization to API
  * Setup the API access policies for you API
  * Define a criteria for Automatic versus manual provisioning
    * Sensitivity of data
    * Limited capacity in thebackend
    * Trust tiers system
  * If the API is for internal use only then do not publish on portal
  * [Twitter](https://developer.twitter.com/)
* API management platforms
  * [ibm api management](https://www.ibm.com/support/knowledgecenter/zh-tw/SSWHYP_3.0.0/com.ibm.apimgmt.overview.doc/api_management_overview.html)
  * [apigee](https://apigee.com/api-management/#/homepage), [mashery](https://www.mashery.com/)
  * [mulesoft](https://www.mulesoft.com/cn/)
* Support
  * Internal only, Public, Monetized
  * Guidance on how solve some common problems (FAQ)
  * Provide best practices
  * Contact forms
  * Bug reporting
  * Build a developer community
    * Social media, blog, forum
* Build v.s. Buy
  * Developer portal is a web applicaton
  * Build option
    * Documentation from swagger/ OAI may be publish as-is
    * For self service provisoning a work flow will need to be designed 
  * Buy option
    * API product vendors offer Developer Portal bunled with their products
    * Support look and feel customization
    * Some have provision to extend the portals