Skip to main content Skip to complementary content

Configuring your portal with another Git provider

To use the API Portal feature with a Git provider other than GitHub, you can download the Starter Kit and your API documentation and push them to your repository.

Downloading the API Portal Starter Kit

Download the API Portal Starter Kit from Talend Cloud to use it with your preferred Git provider. For more information about the contents of the template, see Repository architecture.

Procedure

  1. Log in to Talend Cloud.
  2. Click the user menu in the top right corner of the page and click Downloads, then scroll down to the API Portal tile.
  3. Select API Portal Starter Kit (zip), then click Download and save the file.
    API Portal tile in the Downloads page.
  4. Unzip the file in the repository that you want to use as a source for your portal.
  5. Commit your changes.

Results

Your repository is configured, you can now add your API documentation and customize your portal. For more information, see Customizing your portal.

Downloading your API documentation

Download API documentation and definitions to publish on your portal.

Procedure

  1. Open Talend Cloud API Designer and go to the API Portal tab.
  2. Click Configure the API Portal.
  3. Click Select API Documentation to publish.
    API Portal configuration page.
  4. In the API Portal tab, click the Download button to download documentation for an API and save the file.
    By default, the ZIP file downloaded contains:
    • An index.md file containing the API documentation to be published on the portal.
    • An openapi30.json file and a swagger20.json file containing the API definition in OAS 3.0 and Swagger 2.0 respectively. These files can be downloaded by users from the portal.

    You can select the API definitions to download in the Settings. For more information, see Publishing downloadable API definitions.

    API Portaltab.
  5. Unzip the file in your repository, in the apis folder.
    In the apis folder, you should have a folder for each API and a sub-folder for each API version.
  6. Commit your changes.

Results

You have pushed an API to your repository, you can now deploy your portal.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!