Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Migrating API contracts from the Default repository

Move your API contracts and folders from the Default repository into named repositories, then configure sharing at the repository level to replace contract-level and version-level sharing.

Before you begin

You have the API Designer - Administrate permission or own the API contracts you want to migrate.

About this task

Named repositories are automatically synced between Talend Cloud and Qlik Cloud. The Default repository is not synced. Sharing at the API contract and version levels is also available only in Talend Cloud; this option is not available in Qlik Cloud. Complete this task before migrating to Qlik Cloud to ensure your APIs are synced and your team retains access.

Procedure

  1. Create one or more repositories.
    For more information, see Creating a repository.
  2. Bulk move or copy your APIs and folders from the Default repository to the appropriate new repository.
    For more information, see Moving and copying multiple APIs and folders to another repository.
    Information noteNote: Moved items are automatically unshared in the target repository. Reconfigure sharing at the repository level in the next step.
  3. Configure sharing on each new repository.
    For more information, see Sharing an API repository.
  4. Optional: Hide the Default repository after moving all contracts and folders.
    For more information, see Hiding the Default repository.

Results

Your API contracts are organized in named repositories with repository-level sharing. You must reconfigure at the repository level any sharing settings that were previously configured at the contract or version levels.

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!

Leave your feedback here